git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Kidd <git@randomhacks.net>
To: git@vger.kernel.org
Subject: Re: [PATCHv3] filter-branch: Add more error-handling
Date: Wed, 11 Feb 2009 16:00:18 -0500	[thread overview]
Message-ID: <431341160902111300r1a1c3a22n3c098a7d824a3fca@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0902112145400.10279@pacific.mpi-cbg.de>

On Wed, Feb 11, 2009 at 3:48 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> I haven't checked, but is "$tempdir" not the working directory?  If so,
> this would lead to funny interaction with --tree-filter.  Rather, I'd
> write the file into "$GIT_DIR".  Likewise the other files.

The working directory actually lives one level down:

 tempdir=.git-rewrite
 workdir="$tempdir/t"

At the end of the script, git-filter-branch cleans up all of its
temporary files by deleting $tempdir. There's actually a fair bit of
stuff in there already, and none of it interferes with --tree-filter.

> That's not how it is supposed to be used.  Rather,
>
>        test_expect_success $LABEL '
>                test_must_fail git filter-branc $OPTIONS
>        '

Will fix. Thank you.

I really appreciate all this feedback from the git team. Thank you for
taking the time to help me get this right!

Cheers,
Eric

  reply	other threads:[~2009-02-11 21:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 14:09 [PATCH] git-filter-branch: Add more error-handling Eric Kidd
2009-02-11 14:58 ` Johannes Sixt
2009-02-11 15:36   ` Johannes Sixt
2009-02-11 15:24 ` Johannes Schindelin
2009-02-11 17:15 ` [PATCH v2] filter-branch: " Eric Kidd
2009-02-11 19:03   ` Junio C Hamano
2009-02-11 19:34     ` Eric Kidd
2009-02-11 20:03     ` [PATCHv3] " Eric Kidd
2009-02-11 20:48       ` Johannes Schindelin
2009-02-11 21:00         ` Eric Kidd [this message]
2009-02-11 21:10         ` [PATCHv4] " Eric Kidd
2009-02-11 21:30     ` [PATCH v2] " Nanako Shiraishi
2009-02-11 22:28       ` Junio C Hamano

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=431341160902111300r1a1c3a22n3c098a7d824a3fca@mail.gmail.com \
    --to=git@randomhacks.net \
    --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).