From: Andreas Stricker <astricker@futurelab.ch>
To: bolfo <boflor@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: weird github capitalization problem
Date: Fri, 07 Jan 2011 10:17:06 +0100 [thread overview]
Message-ID: <4D26DA12.50002@futurelab.ch> (raw)
In-Reply-To: <1294146242606-5888573.post@n2.nabble.com>
[-- Attachment #1: Type: text/plain, Size: 2063 bytes --]
Am 04.01.11 14:04, schrieb bolfo:
> I first installed everything on my laptop, coded some stuff and then pushed
> to github. Apparently something went wrong because there was a new
> directory, while at first the directory was OurProjectsources, there now was
> a new directory called OurProjectSources. Weird since my local directory has
> the s not capitalized.
> I work on a windows PC while the original author works on a Mac, could this
> be the problem?
Yes, Mac OSX HFS+ filesystem ignores the case by default (you'll need
to reformat to change this). So OurProjectSources and OurProjectsources
both refers to the same directory on Mac OS X. On Linux there are two
different directories
This frequently causes issues here too. An example:
me@mac:t $ git init r
Initialized empty Git repository in /private/tmp/t/r/.git/
me@mac:r (master) $ mkdir OurProjectsources
me@mac:r (master) $ touch OurProjectsources/a
me@mac:r (master) $ git add OurProjectsources/a
me@mac:r (master) $ git commit -m "initial import"
[master (root-commit) c2cb2f3] initial import
0 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 OurProjectsources/a
me@mac:r (master) $ mv OurProjectsources/ OurProjectSources
me@mac:r (master) $ touch OurProjectSources/b
me@mac:r (master) $ git add OurProjectSources/b
me@mac:r (master) $ git commit -m "added b"
[master 4de780c] added b
0 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 OurProjectSources/b
me@mac:r (master) $ git stat
# On branch master
nothing to commit (working directory clean)
me@mac:r (master) $ scp -r .git linux:t.git
me@mac:r (master) $ ssh linux
me@linux:~ $ git clone t.git/
Initialized empty Git repository in /home/me/t/.git/
me@linux:~ $ cd t
me@linux:~/t $ ls
OurProjectsources OurProjectSources
me@linux:~/t $ find *
OurProjectsources
OurProjectsources/a
OurProjectSources
OurProjectSources/b
And there it is, our mess. The mac user accidentally created
two different directories but didn't see them.
~/Andy
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4722 bytes --]
next prev parent reply other threads:[~2011-01-07 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 13:04 weird github capitalization problem bolfo
2011-01-07 9:17 ` Andreas Stricker [this message]
2011-01-14 12:11 ` Torsten Bögershausen
2011-01-14 15:30 ` Torsten Bögershausen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D26DA12.50002@futurelab.ch \
--to=astricker@futurelab.ch \
--cc=boflor@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).