On 24. mars. 2008, at 16.10, Johannes Schindelin wrote:
[Regarding filter-branch rewriting tags]
You can say "--all", and I actually expect quite a few people to do
exactly that. And then you cannot really say "the user explicitely
asked
to have that signed tag rewritten".
Sorry to hijack the thread. I've seen you mention using "--all" to
filter-branch everything before, but I can't get it to work:
% git filter-branch --all
Usage: /usr/local/bin/git-filter-branch [--env-filter <command>] [--
tree-filter <command>] [--index-filter <command>] [--parent-filter
<command>] [--msg-filter <command>] [--commit-filter <command>] [--tag-
name-filter <command>] [--subdirectory-filter <directory>] [--original
<namespace>] [-d <directory>] [-f | --force] [<rev-list options>...]
I'm trying to rewrite history to match .git/info/grafts without going
through every graft, hence the lack of an actual filter command.
Thinking that might be the problem, I also tried the "update-index --
remove <filename>" example, but it wouldn't let me use "--all" either:
% git filter-branch --index-filter 'git update-index --remove RELEASE-
NOTES' --all
Usage: /usr/local/bin/git-filter-branch [--env-filter <command>] [--
tree-filter <command>] [--index-filter <command>] [--parent-filter
<command>] [--msg-filter <command>] [--commit-filter <command>] [--tag-
name-filter <command>] [--subdirectory-filter <directory>] [--original
<namespace>] [-d <directory>] [-f | --force] [<rev-list options>...]
as opposed to:
% git filter-branch --index-filter 'git update-index --remove RELEASE-
NOTES' HEAD
Rewrite 266da463b4e59eaf06287b36b6435b8218db9f40 (611/4040)
^C
git version 1.5.5.rc0.10.g7881f.dirty (the dirtiness is in git-
submodule.sh, and I've tried it with older, cleaner versions).
Am I just stupid and/or crazy, or does it not work?
--
Eyvind Bernhardsen
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
