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

Re: [BUG?] git revert option parsing too lenient?

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
May 11, 2011, 20:44 UTC
Message-ID
<BANLkTin5FMYJkeLTNeZ47jsXtVxvrLRL+Q@mail.gmail.com>
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
Previous: Jeff KingNext: Jeff King
Message 3 of 5 in “[BUG?] git revert option parsing too lenient?”
  1. Sverre RabbelierMay 11, 2011
  2. Jeff KingMay 11, 2011
  3. Sverre RabbelierMay 11, 2011
  4. Jeff KingMay 11, 2011
  5. Sverre RabbelierMay 11, 2011

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.