URL:
<https://savannah.nongnu.org/task/?15223>
Summary: savane code - 'mechs' vs 'MECHS' name collision on
case-insensitive filesystems
Project: Savannah Administration
Submitted by: None
Submitted on: Wed 27 Mar 2019 08:13:31 PM UTC
Should Start On: Wed 27 Mar 2019 12:00:00 AM UTC
Should be Finished on: Wed 27 Mar 2019 12:00:00 AM UTC
Category: None
Priority: 5 - Normal
Status: None
Privacy: Public
Percent Complete: 0%
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Effort: 0.00
_______________________________________________________
Details:
Hi! First-time Savannah hacker here. Sorry if I've mis-categorized this; it's
a bug report, and doesn't fit well into any of the Category items above.
I'm working on running Savannah locally as described in
http://savannah.gnu.org/maintenance/RunningSavaneLocally/. I'm running a Mac,
where the filesystem is case-insensitive.
There is a tests/mechs directory, and a tests/MECHS documentation text file.
On case-insensitive filesystems, these names collide, and one of them will
disappear from your local git repo and appear deleted.
[savane] $ pwd
/Users/janke/local/repos/savane
[savane] $ git status
On branch master
Your branch is up to date with 'origin/master'.
Changes not staged for commit:
(use "git add/rm <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
deleted: tests/MECHS
Simple fix: rename MECHS to MECHS.txt to avoid the collision. I've done so on
my branch at https://github.com/apjanke/savane/tree/fix-mechs-vs-MECHS. Is
this the right way to submit a pull request?
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/task/?15223>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
