From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Avery Pennarun <apenwarr@gmail.com>,
Frank <streamlake@tiscali.it>,
git@vger.kernel.org
Subject: Re: Cygwin: problem with renaming and case
Date: Fri, 21 Mar 2008 17:32:39 -0700 [thread overview]
Message-ID: <7vtzizmwd4.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0803211105190.3020@woody.linux-foundation.org> (Linus Torvalds's message of "Fri, 21 Mar 2008 11:09:56 -0700 (PDT)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> So I agree, in this case the "remove files that go away first" would work
> around the problem, and we could look into whether that is reasonable in
> some cases, but in general it's not trivial either.
I think we have two phase "remove then create" in git-apply for an
entirely different reason (we do check before doing any removal or
creation).
> My personal guess is that it's probably better to start teaching git about
> case-broken filesystem, even if we start it with some common special case
> rather than getting every case right from the beginning.
Hmm. I have to say I am not very enthused by the prospect, as I agree
with your reasoning in your earlier message why this has been lower
priority ("sane people when forced to use case corrupting systems avoid
problematic paths to make this a non-issue anyway"). My feeling is that
this falls into the "when we are bored to death and have absolutely
nothing better to do" category.
next prev parent reply other threads:[~2008-03-22 0:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 16:07 Cygwin: problem with renaming and case Frank
2008-03-21 17:46 ` Linus Torvalds
2008-03-21 17:57 ` Avery Pennarun
2008-03-21 18:09 ` Linus Torvalds
2008-03-22 0:32 ` Junio C Hamano [this message]
2008-03-22 13:45 ` Steffen Prohaska
2008-03-21 18:57 ` Dmitry Potapov
2008-03-21 19:37 ` streamlake
2008-03-21 19:54 ` Brian Dessent
2008-03-22 19:58 ` Nagy Balázs
2008-03-22 20:18 ` Linus Torvalds
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=7vtzizmwd4.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=streamlake@tiscali.it \
--cc=torvalds@linux-foundation.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