From: Eyvind Bernhardsen Date: Mon, 24 Mar 2008 21:22:46 GMT Subject: filter-branch --all? Message-ID: <263C0D8D-0454-402A-B65C-08E91F7BD5C7@orakel.ntnu.no> In-Reply-To: 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 ] [-- tree-filter ] [--index-filter ] [--parent-filter ] [--msg-filter ] [--commit-filter ] [--tag- name-filter ] [--subdirectory-filter ] [--original ] [-d ] [-f | --force] [...] 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 " 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 ] [-- tree-filter ] [--index-filter ] [--parent-filter ] [--msg-filter ] [--commit-filter ] [--tag- name-filter ] [--subdirectory-filter ] [--original ] [-d ] [-f | --force] [...] 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