git/list[1] front-page[2] threads[3] people[4] search[5] about
 

filter-branch --all?

From
Eyvind Bernhardsen <eyvind-git@orakel.ntnu.no>
Date
Mar 24, 2008, 21:22 UTC
Message-ID
<263C0D8D-0454-402A-B65C-08E91F7BD5C7@orakel.ntnu.no>
In-Reply-To
<alpine.LSU.1.00.0803241609540.4353@racer.site>
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
Previous: Brandon CaseyNext: Brandon Casey
Message 14 of 23 in “filter-branch.sh: support nearly proper tag name filtering”
  1. 2/2 filter-branch.sh: support nearly proper tag name filteringBrandon Casey, Mar 20, 2008
  2. Johannes SchindelinMar 20, 2008
  3. Brandon CaseyMar 20, 2008
  4. Junio C HamanoMar 24, 2008
  5. Johannes SchindelinMar 24, 2008
  6. Junio C HamanoMar 24, 2008
  7. Johannes SchindelinMar 24, 2008
  8. Brandon CaseyMar 24, 2008
  9. Brandon CaseyMar 24, 2008
  10. Johannes SchindelinMar 24, 2008
  11. Brandon CaseyMar 24, 2008
  12. Johannes SchindelinMar 24, 2008
  13. Brandon CaseyMar 24, 2008
  14. filter-branch --all?Eyvind Bernhardsen, Mar 24, 2008
  15. Brandon CaseyMar 24, 2008
  16. Eyvind BernhardsenMar 24, 2008
  17. Brandon CaseyMar 24, 2008
  18. filter-branch.sh: support nearly proper tag name filteringBrandon Casey, Mar 24, 2008
  19. Brandon CaseyMar 24, 2008
  20. Junio C HamanoMar 25, 2008
  21. filter-branch.sh: support nearly proper tag name filteringBrandon Casey, Mar 25, 2008
  22. Junio C HamanoMar 26, 2008
  23. filter-branch.sh: support nearly proper tag name filteringBrandon Casey, Mar 26, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.