All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Andreas Stricker <astricker@futurelab.ch>
Cc: bolfo <boflor@gmail.com>, git@vger.kernel.org, tboegi@web.de
Subject: Re: weird github capitalization problem
Date: Fri, 14 Jan 2011 13:11:09 +0100	[thread overview]
Message-ID: <4D303D5D.6090108@web.de> (raw)
In-Reply-To: <4D26DA12.50002@futurelab.ch>

On 07.01.11 10:17, Andreas Stricker wrote:
> 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
>

The following is on next from git.git:
(And more commits fixing more core.ignorecase issues)
You might give it a try.
HTH
/Torsten



commit 50906e04e8f48215b0b09841686709b92a2ab2e4
Author: Joshua Jensen <jjensen@workspacewhiz.com>
Date:   Sun Oct 3 09:56:46 2010 +0000

     Support case folding in git fast-import when core.ignorecase=true

     When core.ignorecase=true, imported file paths will be folded to match
     existing directory case.

     Signed-off-by: Joshua Jensen <jjensen@workspacewhiz.com>
     Signed-off-by: Johannes Sixt <j6t@kdbg.org>
     Signed-off-by: Junio C Hamano <gitster@pobox.com>

  reply	other threads:[~2011-01-14 12:11 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
2011-01-14 12:11   ` Torsten Bögershausen [this message]
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=4D303D5D.6090108@web.de \
    --to=tboegi@web.de \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.