meaning of HEAD in context of filter-branch
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?
Signature · 4 lines
regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
Quoted 3 lines · bill lam
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.
Signature · 3 lines
Andreas Schwab, [email protected] GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Quoted 2 lines · Andreas Schwab
reasons). Prior to that, the $GIT_COMMIT environment variable will be
^^^^^^^^^^^
Thanks. This is what I should use.
Signature · 4 lines
regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3