From: Lars Noschinski <lars@public.noschinski.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] filter-branch -d: Export GIT_DIR earlier
Date: Tue, 17 Feb 2009 18:59:59 +0100 [thread overview]
Message-ID: <20090217175959.GA3564@lars.home.noschinski.de> (raw)
In-Reply-To: <alpine.DEB.1.00.0902171327270.6185@intel-tinevez-2-302>
* Johannes Schindelin <Johannes.Schindelin@gmx.de> [09-02-17 16:08]:
>On Tue, 17 Feb 2009, Lars Noschinski wrote:
>> The improved error handling catches a bug in filter-branch when using
>> -d pointing to a path outside any git repository:
>>
>> $ mkdir foo
>> $ cd foo
>> $ git init
>> $ touch bar
>> $ git add bar
>> $ git commit -m bar
>> $ cd ..
>> $ git clone --bare foo
>> $ cd foo.git
>> $ git filter-branch -d /tmp/filter master
>> fatal: Not a git repository (or any of the parent directories): .git
>
>This could be written as
>
> $ cd .git
> $ git filter-branch -d /tmp/bla master
Does not work, as we get another (slightly misleading) error message:
/tmp/foo/.git$ git filter-branch -d /tmp/bar master
fatal: This operation must be run in a work tree
Cannot rewrite branch(es) with a dirty working directory.
But we do not need a bare repository at all to demonstrate this bug, so
we can skip even the 'cd .git'.
>Funny, git am -3 reports:
>
> Did you hand edit your patch?
> It does not apply to blobs recorded in its index.
> Cannot fall back to three-way merge.
Hm, for some reason, format=flowed was enabled. I wonder, that it has
not bitten me earlier.
>We try to avoid cd'ing back, by using constructs like this:
>
> (cd drepo &&
> ...
> ) &&
Ok, can do.
>After those two (maybe three) changes and your SOB: ACK.
>
>BTW the reason I wanted to test this thing is that I suspected that you
>meant test_commit instead of make_commit. But then, I realized that there
>exists a make_commit in t7003... which shares the shortcoming of our
>previous implementation of test_commit in that it adds ambiguities on
>case-insensitive filesystems.
Yeah, I used make_commit to stay consistent with the rest of the file.
I'll change it to test_commit. I think as it does not bite us, it would
be unnecessary code churn to remove the remaining usage of make_commit?
>So I _had_ to look who introduced make_commit:
>
> $ git blame -L '/make_commit/,/}/' t/t7003*
>
>Making a fool out of yourself -- priceless.
:)
- Lars.
next prev parent reply other threads:[~2009-02-17 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 8:31 [PATCH v2] filter-branch -d: Export GIT_DIR earlier Lars Noschinski
2009-02-17 8:53 ` Lars Noschinski
2009-02-17 12:44 ` Johannes Schindelin
2009-02-17 17:59 ` Lars Noschinski [this message]
2009-02-17 18:05 ` [PATCH v3] " Lars Noschinski
2009-02-17 23:03 ` Johannes Schindelin
2009-02-18 8:35 ` [PATCH v4] " Lars Noschinski
2009-02-18 10:25 ` Johannes Schindelin
2009-02-19 0:53 ` Junio C Hamano
2009-02-17 23:01 ` [PATCH v2] " Johannes Schindelin
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=20090217175959.GA3564@lars.home.noschinski.de \
--to=lars@public.noschinski.de \
--cc=Johannes.Schindelin@gmx.de \
--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.
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).