Re: Trouble with case-insensitive filesystems

From: Rocco Rutte <pdmef@gmx.net>
Date: Oct 26, 2007, 16:11 UTC
Message-ID: <20071026161136.GC294@localhost.daprodeges.fqdn.th-h.de>
In-Reply-To: <4722064C.1000201@op5.se>

Hi,

* Andreas Ericsson [07-10-26 17:22:52 +0200] wrote:

Show 7 quoted lines

> There are no areas in git to patch. There's no sane way to handle your
> case, so the best you could opt for is to import it to a system with
> sane case-handling, alter the repo so no two filenames clash, and then
> check it out on your case-insensitive filesystem. Note that you'll
> have to make sure that you never check anything out prior to the
> commit that renames the case-name clashes, or you'll end up with this
> same trouble all over again.

Personally I don't have a problem with that (since I do no work with that repo). But IMHO it's bad to leave people without a clue what could be wrong when git-status right after git-checkout/git-clone reports changes. Btw, mercurial reports the problem so immediately know what's wrong.

> On a side note; Please don't set the Reply-To: header for mails to
> git@vger.kernel.org. Some consider it rude, and it makes the ones
> you're asking for help have to work if they want to provide you
> with anything off-list. It's a tad rude.

I didn't set a Reply-To: header, just Mail-Followup-To: which is exactly what I want (in mutt language): Private mails via reply only go to me and list-reply goes to the list.

Rocco