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

Re: [PATCH 1/3] help: use parseopt

From
Jeff King <peff@peff.net>
Date
Feb 25, 2008, 06:57 UTC
Message-ID
<20080225065710.GA3765@coredump.intra.peff.net>
In-Reply-To
<200802250750.53047.chriscool@tuxfamily.org>
On Mon, Feb 25, 2008 at 07:50:52AM +0100, Christian Couder wrote:
> > Sorry, the diff turned out quite messy because of the cleanups. It's
> > probably easier to just read the result.
> 
> Or could you send the cleanups in some separated patches ?

Looking at it again, it's actually not too bad except for the cmd_help() function itself, which isn't due to the cleanups at all, but because the flow changes quite a bit. So I don't think splitting it actually will make the diff any friendlier.

-Peff
Previous: Christian CouderNext: Junio C Hamano
Message 3 of 12 in “help: use parseopt”
  1. 1/3 help: use parseoptJeff King, Feb 24, 2008
  2. Christian CouderFeb 25, 2008
  3. Jeff KingFeb 25, 2008
  4. Junio C HamanoFeb 25, 2008
  5. 2/3 make alias lookup a public, procedural functionJeff King, Feb 24, 2008
  6. 3/3 help: respect aliasesJeff King, Feb 24, 2008
  7. Jay SoffianFeb 25, 2008
  8. Johannes SchindelinFeb 26, 2008
  9. Jay SoffianFeb 26, 2008
  10. Johannes SchindelinFeb 26, 2008
  11. Junio C HamanoFeb 26, 2008
  12. Jay SoffianFeb 26, 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.