git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Simeon Maxein <smaxein@googlemail.com>
To: git@vger.kernel.org
Subject: git filter-branch can "forget" directories on case insensitive filesystems
Date: Fri, 3 Sep 2010 18:36:17 +0200	[thread overview]
Message-ID: <AANLkTimOs9m==KaD3BNHcgkTTqNQF1yV0NLA_Ew+iS-N@mail.gmail.com> (raw)

When running git filter-branch on a case insensitive filesystem, the
working tree checked out for filtering is missing a directory in my
project. This is probably related to the problem discussed here:
http://article.gmane.org/gmane.comp.version-control.git/154662

In contrast to that report, this one affects repositories on
case-insensitive filesystems, regardless of the setting of
core.ignorecase.

To reproduce the problem, follow the steps below. I tested them with
git 1.7.0.4 on a laptop running Ubuntu, with the repository on a Fat32
USB drive.

mkdir gittest
cd gittest
git init
mkdir testdir
echo 'abc' >testdir/testfile
git add testdir
git commit -m foo
git rm -r testdir
mkdir testDir
echo 'abc' >testDir/testfile
git add testDir
git commit -m bar

Now, check out master^1 and master to ensure the commits look as
expected. Then, run this:

git filter-branch --tree-filter 'ls' master

You will notice that the directory vanishes when the second commit is filtered.

The problem occurs whether core.ignorecase is set to true or false. It
doesn't occur on case sensitive filesystems.

Simeon

             reply	other threads:[~2010-09-03 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 16:36 Simeon Maxein [this message]
2011-01-25 20:56 ` git filter-branch can "forget" directories on case insensitive filesystems Simeon Maxein
2011-01-25 21:56   ` Johannes Sixt
2011-01-25 23:26     ` Simeon Maxein
2011-01-25 23:31       ` Erik Faye-Lund
2011-01-26  0:24         ` Simeon Maxein
2011-01-26  0:58           ` Erik Faye-Lund

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='AANLkTimOs9m==KaD3BNHcgkTTqNQF1yV0NLA_Ew+iS-N@mail.gmail.com' \
    --to=smaxein@googlemail.com \
    --cc=git@vger.kernel.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).