-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upper case and lower case file names #9
Comments
…date from the source and under Microsoft Windows.
The commit 251d7c8 chose the file for the lower-case name that received the most recent changes, even if this technically reverts what has already been in there a newer version synced from the source earlier, while the older one still received more recent changes, under the assumption that the only remaining file with lower-case name will get updated from the source again (by overwrite because of the same file name and character case of the Markdown source). Files with upper-case names that don't have a lower-case equivalent weren't moved even if they obviously got renamed in the source to reflect that they're patterns, which can be the next step for this issue. |
|
There are several files in the repository that differ in their name only by upper and lower case. On Unix-based operating systems, they're treated as different, separate files, where the $/en/peeragogy-shell.tex refers the (outdated) upper-case variants, while the new versions from the Peeragogy.github.io repository are named in lower-case. Under Microsoft Windows, on extracting the downloaded .zip, the files are considered to be duplicates, asking the user if to keep the first variant or overwrite it with the second, or rename (then without effect in regard to the peeragogy-shell.tex).
Adjust + expect names according to the Peeragogy.github.io repository as the source, get rid of the other files?
The text was updated successfully, but these errors were encountered: