git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
	kusmabite@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH v2] Allow git mv FileA fILEa on case ignore file systems
Date: Tue, 12 Apr 2011 08:16:12 +0200	[thread overview]
Message-ID: <4DA3EE2C.2010702@viscovery.net> (raw)
In-Reply-To: <7vd3ksybfr.fsf@alter.siamese.dyndns.org>

Am 4/11/2011 18:55, schrieb Junio C Hamano:
> Yeah, I forgot about the primary thing we are trying to do in this
> discussion.  Sorry about that.  My thinking stopped at 'if we rename "A"
> to "a in the index, that is sufficient.  We already know that we can still
> open("A") because the filesystem is case insensitive.'
> 
> In fact, we want both the index entry "A" renamed to "a" _and_ also we
> want to see next "/bin/ls" to show "a", not "A".  For the latter, we do
> want to run rename(2) on them.

I wonder why we need this at all. You can always break this into two
operations:

  git mv A a1
  git mv a1 a

Is 'git mv A a' on a case-insensitive filesystem such an every-day
operation that we have to provide special support for it in git?

-- Hannes

      parent reply	other threads:[~2011-04-12  6:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19 14:28 [PATCH v2] Allow git mv FileA fILEa on case ignore file systems Torsten Bögershausen
2011-03-19 18:20 ` Erik Faye-Lund
2011-03-19 19:30   ` Piotr Krukowiecki
2011-03-20  5:50 ` Junio C Hamano
2011-04-10  5:48   ` Torsten Bögershausen
2011-04-11 16:55     ` Junio C Hamano
2011-04-11 20:05       ` Torsten Bögershausen
2011-04-12  6:16       ` Johannes Sixt [this message]

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=4DA3EE2C.2010702@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kusmabite@gmail.com \
    --cc=tboegi@web.de \
    /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).