From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Document git-filter-branch
Date: Wed, 11 Jul 2007 18:53:29 +0200 [thread overview]
Message-ID: <f731u9$1ir$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0707040004200.4071@racer.site
[Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Frank Lichtenheld <frank@lichtenheld.de>]
Johannes Schindelin wrote:
> On Wed, 4 Jul 2007, Frank Lichtenheld wrote:
>>> +Note that since this operation is extensively I/O expensive, it might
>>> +be a good idea to redirect the temporary directory it off-disk, e.g. on
By the way, could git-filter-branch use git-fast-import to reduce I/O?
>>> +the id of the commit being rewritten. The author/committer environment
>>> +variables are set before the first filter is run.
>>
>> Maybe give the actual names of the environment variables here?
>
> If you think so:
>
> Also, GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_AUTHOR_DATE,
> GIT_COMMITTER_NAME, GIT_COMMITTER_EMAIL, and GIT_COMMITTER_DATE is
> set according to the current commit.
Or
Also, GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_AUTHOR_DATE,
GIT_COMMITTER_NAME, GIT_COMMITTER_EMAIL, and GIT_COMMITTER_DATE
are filled with data taken from the current commit.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-07-11 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 16:47 [PATCH] Document git-filter-branch Johannes Schindelin
2007-07-03 22:05 ` Frank Lichtenheld
2007-07-03 23:17 ` Johannes Schindelin
2007-07-04 11:29 ` Frank Lichtenheld
2007-07-04 14:50 ` [PATCH] filter-branch: a few more touch ups to the man page Johannes Schindelin
2007-07-04 15:06 ` Frank Lichtenheld
2007-07-11 16:53 ` Jakub Narebski [this message]
2007-07-11 17:03 ` [PATCH] Document git-filter-branch Johannes Schindelin
2007-07-03 23:41 ` Johannes Schindelin
2007-07-04 7:32 ` [PATCH] filter-branch documentation: some more touch-ups Johannes Sixt
2007-07-04 10:58 ` Johannes Schindelin
2007-07-04 16:56 ` 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='f731u9$1ir$1@sea.gmane.org' \
--to=jnareb@gmail.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.
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).