{"thread":{"id":"26187","subject":"weird github capitalization problem","startedAt":"2011-01-04T13:04:02Z","lastAt":"2011-01-14T15:30:24Z","messageCount":4,"participants":["bolfo","Andreas Stricker","Torsten Bögershausen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"158887","messageId":"1294146242606-5888573.post@n2.nabble.com","threadId":"26187","inReplyTo":null,"subject":"weird github capitalization problem","fromName":"bolfo","fromEmail":"boflor@gmail.com","sentAt":"2011-01-04T13:04:02Z","receivedAt":"2011-01-04T13:04:02Z","isPatch":false,"sender":{"key":"boflor@gmail.com","avatar":null},"body":"\nHello guys,\n\nI am new at git and github, but I am collaborating on a netbeans java\nproject with someone else and we host our code on github.\nI first installed everything on my laptop, coded some stuff and then pushed\nto github. Apparently something went wrong because there was a new\ndirectory, while at first the directory was OurProjectsources, there now was\na new directory called OurProjectSources. Weird since my local directory has\nthe s not capitalized.\nI installed git on another PC and cloned the project from github to my local\nPC.\nApparently only the directory with the capital S was pulled.\n\nDoes anyone recognize this problem? \nI work on a windows PC while the original author works on a Mac, could this\nbe the problem?\n-- \nView this message in context: http://git.661346.n2.nabble.com/weird-github-capitalization-problem-tp5888573p5888573.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"159099","messageId":"4D26DA12.50002@futurelab.ch","threadId":"26187","inReplyTo":"1294146242606-5888573.post@n2.nabble.com","subject":"Re: weird github capitalization problem","fromName":"Andreas Stricker","fromEmail":"astricker@futurelab.ch","sentAt":"2011-01-07T09:17:06Z","receivedAt":"2011-01-07T09:17:06Z","isPatch":false,"sender":{"key":"astricker@futurelab.ch","avatar":"https://gravatar.com/avatar/007ac93f9abc20ee78c5169783fcf3f065d470d6b53d47050e30cf7ebad5025b?d=mp&s=160"},"body":"Am 04.01.11 14:04, schrieb bolfo:\n> I first installed everything on my laptop, coded some stuff and then pushed\n> to github. Apparently something went wrong because there was a new\n> directory, while at first the directory was OurProjectsources, there now was\n> a new directory called OurProjectSources. Weird since my local directory has\n> the s not capitalized.\n\n> I work on a windows PC while the original author works on a Mac, could this\n> be the problem?\n\nYes, Mac OSX HFS+ filesystem ignores the case by default (you'll need\nto reformat to change this). So OurProjectSources and OurProjectsources\nboth refers to the same directory on Mac OS X. On Linux there are two\ndifferent directories\n\nThis frequently causes issues here too. An example:\n\nme@mac:t $ git init r\nInitialized empty Git repository in /private/tmp/t/r/.git/\nme@mac:r (master) $ mkdir OurProjectsources\nme@mac:r (master) $ touch OurProjectsources/a\nme@mac:r (master) $ git add OurProjectsources/a\nme@mac:r (master) $ git commit -m \"initial import\"\n[master (root-commit) c2cb2f3] initial import\n 0 files changed, 0 insertions(+), 0 deletions(-)\n create mode 100644 OurProjectsources/a\nme@mac:r (master) $ mv OurProjectsources/ OurProjectSources\nme@mac:r (master) $ touch OurProjectSources/b\nme@mac:r (master) $ git add OurProjectSources/b\nme@mac:r (master) $ git commit -m \"added b\"\n[master 4de780c] added b\n 0 files changed, 0 insertions(+), 0 deletions(-)\n create mode 100644 OurProjectSources/b\nme@mac:r (master) $ git stat\n# On branch master\nnothing to commit (working directory clean)\nme@mac:r (master) $ scp -r .git linux:t.git\nme@mac:r (master) $ ssh linux\n\nme@linux:~ $ git clone t.git/\nInitialized empty Git repository in /home/me/t/.git/\nme@linux:~ $ cd t\nme@linux:~/t $ ls\nOurProjectsources OurProjectSources\nme@linux:~/t $ find *\nOurProjectsources\nOurProjectsources/a\nOurProjectSources\nOurProjectSources/b\n\nAnd there it is, our mess. The mac user accidentally created\ntwo different directories but didn't see them.\n\n~/Andy\n\n"},{"id":"159481","messageId":"4D303D5D.6090108@web.de","threadId":"26187","inReplyTo":"4D26DA12.50002@futurelab.ch","subject":"Re: weird github capitalization problem","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2011-01-14T12:11:09Z","receivedAt":"2011-01-14T12:11:09Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On 07.01.11 10:17, Andreas Stricker wrote:\n> Am 04.01.11 14:04, schrieb bolfo:\n>> I first installed everything on my laptop, coded some stuff and then pushed\n>> to github. Apparently something went wrong because there was a new\n>> directory, while at first the directory was OurProjectsources, there now was\n>> a new directory called OurProjectSources. Weird since my local directory has\n>> the s not capitalized.\n>\n>> I work on a windows PC while the original author works on a Mac, could this\n>> be the problem?\n>\n> Yes, Mac OSX HFS+ filesystem ignores the case by default (you'll need\n> to reformat to change this). So OurProjectSources and OurProjectsources\n> both refers to the same directory on Mac OS X. On Linux there are two\n> different directories\n>\n> This frequently causes issues here too. An example:\n>\n> me@mac:t $ git init r\n> Initialized empty Git repository in /private/tmp/t/r/.git/\n> me@mac:r (master) $ mkdir OurProjectsources\n> me@mac:r (master) $ touch OurProjectsources/a\n> me@mac:r (master) $ git add OurProjectsources/a\n> me@mac:r (master) $ git commit -m \"initial import\"\n> [master (root-commit) c2cb2f3] initial import\n> 0 files changed, 0 insertions(+), 0 deletions(-)\n> create mode 100644 OurProjectsources/a\n> me@mac:r (master) $ mv OurProjectsources/ OurProjectSources\n> me@mac:r (master) $ touch OurProjectSources/b\n> me@mac:r (master) $ git add OurProjectSources/b\n> me@mac:r (master) $ git commit -m \"added b\"\n> [master 4de780c] added b\n> 0 files changed, 0 insertions(+), 0 deletions(-)\n> create mode 100644 OurProjectSources/b\n> me@mac:r (master) $ git stat\n> # On branch master\n> nothing to commit (working directory clean)\n> me@mac:r (master) $ scp -r .git linux:t.git\n> me@mac:r (master) $ ssh linux\n>\n> me@linux:~ $ git clone t.git/\n> Initialized empty Git repository in /home/me/t/.git/\n> me@linux:~ $ cd t\n> me@linux:~/t $ ls\n> OurProjectsources OurProjectSources\n> me@linux:~/t $ find *\n> OurProjectsources\n> OurProjectsources/a\n> OurProjectSources\n> OurProjectSources/b\n>\n> And there it is, our mess. The mac user accidentally created\n> two different directories but didn't see them.\n>\n> ~/Andy\n>\n\nThe following is on next from git.git:\n(And more commits fixing more core.ignorecase issues)\nYou might give it a try.\nHTH\n/Torsten\n\n\n\ncommit 50906e04e8f48215b0b09841686709b92a2ab2e4\nAuthor: Joshua Jensen \nDate: Sun Oct 3 09:56:46 2010 +0000\n\n Support case folding in git fast-import when core.ignorecase=true\n\n When core.ignorecase=true, imported file paths will be folded to match\n existing directory case.\n\n Signed-off-by: Joshua Jensen \n Signed-off-by: Johannes Sixt \n Signed-off-by: Junio C Hamano \n"},{"id":"159491","messageId":"4D306C10.4000103@gmail.com","threadId":"26187","inReplyTo":"4D303D5D.6090108@web.de","subject":"Re: weird github capitalization problem","fromName":"Torsten Bögershausen","fromEmail":"totte.enea@gmail.com","sentAt":"2011-01-14T15:30:24Z","receivedAt":"2011-01-14T15:30:24Z","isPatch":false,"sender":{"key":"totte.enea@gmail.com","avatar":null},"body":"On 14.01.11 13:11, Torsten Bögershausen wrote:\n> On 07.01.11 10:17, Andreas Stricker wrote:\n>> Am 04.01.11 14:04, schrieb bolfo:\n>>> I first installed everything on my laptop, coded some stuff and then\n>>> pushed\n>>> to github. Apparently something went wrong because there was a new\n>>> directory, while at first the directory was OurProjectsources, there\n>>> now was\n>>> a new directory called OurProjectSources. Weird since my local\n>>> directory has\n>>> the s not capitalized.\n>>\n>>> I work on a windows PC while the original author works on a Mac,\n>>> could this\n>>> be the problem?\n>>\n>> Yes, Mac OSX HFS+ filesystem ignores the case by default (you'll need\n>> to reformat to change this). So OurProjectSources and OurProjectsources\n>> both refers to the same directory on Mac OS X. On Linux there are two\n>> different directories\n>>\n>> This frequently causes issues here too. An example:\n>>\n>> me@mac:t $ git init r\n>> Initialized empty Git repository in /private/tmp/t/r/.git/\n>> me@mac:r (master) $ mkdir OurProjectsources\n>> me@mac:r (master) $ touch OurProjectsources/a\n>> me@mac:r (master) $ git add OurProjectsources/a\n>> me@mac:r (master) $ git commit -m \"initial import\"\n>> [master (root-commit) c2cb2f3] initial import\n>> 0 files changed, 0 insertions(+), 0 deletions(-)\n>> create mode 100644 OurProjectsources/a\n>> me@mac:r (master) $ mv OurProjectsources/ OurProjectSources\n>> me@mac:r (master) $ touch OurProjectSources/b\n>> me@mac:r (master) $ git add OurProjectSources/b\n>> me@mac:r (master) $ git commit -m \"added b\"\n>> [master 4de780c] added b\n>> 0 files changed, 0 insertions(+), 0 deletions(-)\n>> create mode 100644 OurProjectSources/b\n>> me@mac:r (master) $ git stat\n>> # On branch master\n>> nothing to commit (working directory clean)\n>> me@mac:r (master) $ scp -r .git linux:t.git\n>> me@mac:r (master) $ ssh linux\n>>\n>> me@linux:~ $ git clone t.git/\n>> Initialized empty Git repository in /home/me/t/.git/\n>> me@linux:~ $ cd t\n>> me@linux:~/t $ ls\n>> OurProjectsources OurProjectSources\n>> me@linux:~/t $ find *\n>> OurProjectsources\n>> OurProjectsources/a\n>> OurProjectSources\n>> OurProjectSources/b\n>>\n>> And there it is, our mess. The mac user accidentally created\n>> two different directories but didn't see them.\n>>\n>> ~/Andy\n>>\n>\n> The following is on next from git.git:\n> (And more commits fixing more core.ignorecase issues)\n> You might give it a try.\n> HTH\n> /Torsten\n>\n>\n>\n> commit 50906e04e8f48215b0b09841686709b92a2ab2e4\n> Author: Joshua Jensen \n> Date: Sun Oct 3 09:56:46 2010 +0000\n>\n> Support case folding in git fast-import when core.ignorecase=true\n>\n> When core.ignorecase=true, imported file paths will be folded to match\n> existing directory case.\n>\n> Signed-off-by: Joshua Jensen \n> Signed-off-by: Johannes Sixt \n> Signed-off-by: Junio C Hamano \n>\n>\n>\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\nHm,\nthat didn't work.\n\nSee the test on my linux box, after the clone:\n\n\nconfig core.ignorecase true && rm -rf * && git reset --hard && ls && git \nconfig core.ignorecase\nHEAD is now at 2dac314 Added b\nOurProjectsources OurProjectSources\ntrue\n\n\n git --version\ngit version 1.7.2.1.105.g50906\n\nMore work seems to be needed, sorry for the noise.\n/Torsten\n"}]}