From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jonathan del Strother <maillist@steelskies.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [BUG] git-filter-branch and filename case changes on insensitive file systems
Date: Wed, 10 Oct 2007 14:39:44 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710101436570.4174@racer.site> (raw)
In-Reply-To: <80A15F58-5A53-419B-9E22-E967CD590A12@steelskies.com>
Hi,
On Wed, 10 Oct 2007, Jonathan del Strother wrote:
> My repo has a change where a directory named Src was renamed to src.
That is no problem for git-filter-branch.
> I'm using case insensitive HFS+.
That is the problem.
Of course, we could work around that in git, but frankly, you will turn
into problems once you have files whose names differ only in case. And I
am certain somebody will come soon and report this as a bug in git!
I vote for wont-fix (or more accurately "invalid") in git and
please-fix-in-your-setup.
Ciao,
Dscho
next prev parent reply other threads:[~2007-10-10 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 9:40 [BUG] git-filter-branch and filename case changes on insensitive file systems Jonathan del Strother
2007-10-10 13:39 ` Johannes Schindelin [this message]
2007-10-10 13:49 ` Jonathan del Strother
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=Pine.LNX.4.64.0710101436570.4174@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=maillist@steelskies.com \
/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).