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

Re: filter-branch vs. <rev-list options>

From
Jeff King <peff@peff.net>
Date
Mar 2, 2012, 01:00 UTC
Message-ID
<20120302010019.GD21835@sigill.intra.peff.net>
In-Reply-To
<4F50089B.1090202@cisco.com>
On Thu, Mar 01, 2012 at 06:39:07PM -0500, Phil Hord wrote:
Show 9 quoted lines
> git-filter-branch seems to be parsing its own switches and not
> recognizing when they run out and the rest are "rev-list" options. 
> 
> Is there a way to force this break, or should I just expect to have to
> rewrite the logic so that there's always a non-switch argument at the
> start of the rev-list section?  Or am I just doing this wrong?
> 
> fwiw - I'm actually wanting to do this in a script:
>     git filter-branch --msg-filter cat --not --remotes --not "$@"
Did you try "--":
  git filter-branch --msg-filter cat -- --not --remotes --not "$@"
?
Previous: Phil Hord
Message 2 of 2 in “filter-branch vs. <rev-list options>”
  1. Phil HordMar 1, 2012
  2. Jeff KingMar 2, 2012

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.