From: Sverre Rabbelier <srabbelier@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [BUG?] git revert option parsing too lenient?
Date: Wed, 11 May 2011 22:44:48 +0200 [thread overview]
Message-ID: <BANLkTin5FMYJkeLTNeZ47jsXtVxvrLRL+Q@mail.gmail.com> (raw)
In-Reply-To: <20110511203645.GB28742@sigill.intra.peff.net>
Heya,
On Wed, May 11, 2011 at 22:36, Jeff King <peff@peff.net> wrote:
> So yeah, it's a bug, but it is a known one. The trouble is that fixing
> it means splitting the revision options into a set of "these are OK for
> picking a revision or range of revisions" and "other options", and
> letting commands like revert use one set but not the other.
Doing the splitting doesn't sound that hard, I assume the real problem
is getting the option parser to look through both tables?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2011-05-11 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 10:40 [BUG?] git revert option parsing too lenient? Sverre Rabbelier
2011-05-11 20:36 ` Jeff King
2011-05-11 20:44 ` Sverre Rabbelier [this message]
2011-05-11 20:48 ` Jeff King
2011-05-11 20:51 ` Sverre Rabbelier
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=BANLkTin5FMYJkeLTNeZ47jsXtVxvrLRL+Q@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).