* meaning of HEAD in context of filter-branch
@ 2009-10-11 2:43 bill lam
2009-10-11 9:38 ` Andreas Schwab
0 siblings, 1 reply; 3+ messages in thread
From: bill lam @ 2009-10-11 2:43 UTC (permalink / raw)
To: git
I tried to process some files that changed between each commit using
the command
git filter-branch --tree-filter 'git diff --name-only HEAD^.. | foo
however it seems that HEAD is fixed to mean the HEAD of the current
tip before starting git-filter-branch, by trying like this
$ git rev-list -1 HEAD^
2bf95faed2d51c338ea6fa93e7bb6cc9c1bc759b
git filter-branch --tree-filter 'git rev-list -1 HEAD^ >>/tmp/sha' -- --all
$ cat /tmp/sha
2bf95faed2d51c338ea6fa93e7bb6cc9c1bc759b
2bf95faed2d51c338ea6fa93e7bb6cc9c1bc759b
2bf95faed2d51c338ea6fa93e7bb6cc9c1bc759b
2bf95faed2d51c338ea6fa93e7bb6cc9c1bc759b
how to get the HEAD during filter-branch or other workaround?
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: meaning of HEAD in context of filter-branch
2009-10-11 2:43 meaning of HEAD in context of filter-branch bill lam
@ 2009-10-11 9:38 ` Andreas Schwab
2009-10-12 10:41 ` bill lam
0 siblings, 1 reply; 3+ messages in thread
From: Andreas Schwab @ 2009-10-11 9:38 UTC (permalink / raw)
To: bill lam; +Cc: git
bill lam <cbill.lam@gmail.com> writes:
> how to get the HEAD during filter-branch or other workaround?
>From git-filter-index(1):
Filters
The filters are applied in the order as listed below. The <command>
argument is always evaluated in the shell context using the eval
command (with the notable exception of the commit filter, for technical
reasons). Prior to that, the $GIT_COMMIT environment variable will be
^^^^^^^^^^^
set to contain the id of the commit being rewritten.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: meaning of HEAD in context of filter-branch
2009-10-11 9:38 ` Andreas Schwab
@ 2009-10-12 10:41 ` bill lam
0 siblings, 0 replies; 3+ messages in thread
From: bill lam @ 2009-10-12 10:41 UTC (permalink / raw)
To: Andreas Schwab; +Cc: git, bill lam
On Sun, 11 Oct 2009, Andreas Schwab wrote:
> reasons). Prior to that, the $GIT_COMMIT environment variable will be
> ^^^^^^^^^^^
Thanks. This is what I should use.
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-10-12 10:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-10-11 2:43 meaning of HEAD in context of filter-branch bill lam
2009-10-11 9:38 ` Andreas Schwab
2009-10-12 10:41 ` bill lam
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).