From: Jeff King <peff@peff.net>
To: Phil Hord <hordp@cisco.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: filter-branch vs. <rev-list options>
Date: Thu, 1 Mar 2012 20:00:19 -0500 [thread overview]
Message-ID: <20120302010019.GD21835@sigill.intra.peff.net> (raw)
In-Reply-To: <4F50089B.1090202@cisco.com>
On Thu, Mar 01, 2012 at 06:39:07PM -0500, Phil Hord wrote:
> 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 "$@"
?
prev parent reply other threads:[~2012-03-02 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 23:39 filter-branch vs. <rev-list options> Phil Hord
2012-03-02 1:00 ` Jeff King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120302010019.GD21835@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hordp@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).