From: Johan Herland <johan@herland.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Shawn Pearce <spearce@spearce.org>
Subject: Re: RFD: Handling case-colliding filenames on case-insensitive filesystems
Date: Thu, 24 Feb 2011 09:50:27 +0100 [thread overview]
Message-ID: <201102240950.27139.johan@herland.net> (raw)
In-Reply-To: <7v8vx643z4.fsf@alter.siamese.dyndns.org>
On Thursday 24 February 2011, Junio C Hamano wrote:
> Johan Herland <johan@herland.net> writes:
> > On Wednesday 23 February 2011, Junio C Hamano wrote:
> >> I think two things are sensible to do, are relatively low hanging
> >> fruits,
> >>
> >> and are of low risk:
> >> - break checkout on such a tree on incapable filesystems; and
> >
> > Wouldn't that be a regression from the current state (where the poor
> > user in a case-insensitive worktree can at least "git rm" the
> > offending files, and keep working without assistance from a
> > case-sensitive worktree)?
>
> Depends on the definition of "break". I meant "exit with non-zero
> status", not necessarily changing what is left in the working tree from
> what the current code gives us.
Ah, ok. I have no problem with that.
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
next prev parent reply other threads:[~2011-02-24 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 17:11 RFD: Handling case-colliding filenames on case-insensitive filesystems Johan Herland
2011-02-23 18:56 ` Junio C Hamano
2011-02-23 19:01 ` Shawn Pearce
2011-02-23 19:27 ` Junio C Hamano
2011-02-24 0:58 ` Johan Herland
2011-02-24 1:26 ` Junio C Hamano
2011-02-24 8:50 ` Johan Herland [this message]
2011-02-23 19:07 ` Jay Soffian
2011-02-23 19:17 ` Matthieu Moy
2011-02-23 22:52 ` Marc Branchaud
2011-02-23 23:09 ` Greg Troxel
2011-02-24 0:30 ` Johan Herland
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201102240950.27139.johan@herland.net \
--to=johan@herland.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).