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

Re: [PATCH] convert shortlog to use parse_options

From
Pierre Habouzit <madcoder@debian.org>
Date
Mar 2, 2008, 08:11 UTC
Message-ID
<20080302081139.GA5407@artemis.madism.org>
In-Reply-To
<20080302061541.GA3935@coredump.intra.peff.net>
On Sun, Mar 02, 2008 at 06:15:42AM +0000, Jeff King wrote:
Show 9 quoted lines
> #define OPT__REVISION(x) \
>         OPT_BOOLEAN(0, "no-merges", &(x)->no_merges, "don't show merges"),
>         OPT_BOOLEAN(0, "boundary", &(x)->boundary, "show boundary commits"),
>         ...
> 
> and we could have unified options tables. I seem to recall some work
> being done in this area early on in the parse-options history, but I
> can't seem to find any mention of it in the list archive. Pierre, does
> this ring a bell?
  Yes, I didn't had the time to finish that, I just started some ground
works in the diff options area, I hope I didn't lost that work, it's
probably somewhere on my public repository. Though revision parsing are
special because of --not, but I think the proper solution wrt --not and
--all in revision parsing is to ask parse-opt to "let" some options stay
as arguments, and do the final revision parsing with them kept.
  Like you may have noticed, I didn't have a lot of time for git
recently, and that's a shame :| But maybe your mail will beat me into
working on this again now that 1.5.4 is released, because I also feared
that reworking diff and revision parsing options will probably introduce
quite a few regressions, and it's rather better doing so at the
beginning of a release cycle :)
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org
Previous: Jeff KingNext: Pierre Habouzit
Message 4 of 5 in “convert shortlog to use parse_options”
  1. convert shortlog to use parse_optionsJeff King, Mar 1, 2008
  2. Junio C HamanoMar 1, 2008
  3. Jeff KingMar 2, 2008
  4. Pierre HabouzitMar 2, 2008
  5. Pierre HabouzitMar 2, 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.