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

Re: [PATCH] git-branch --with=commit

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 8, 2007, 02:05 UTC
Message-ID
<7vk5ot7aqz.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<Pine.LNX.4.64.0711080008050.4362@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> would it not be better to call it --containing=commit?  Besides, I think 
> that the opt_parse_with_commit() function would be better named 
> opt_parse_commit() and be put into parse-options.[ch].

git-describe has "--contains" so that may be a better match. I do not know the particular function is generic enough to be in parse-options.

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 4 of 9 in “git-branch --with=commit”
  1. git-branch --with=commitJunio C Hamano, Nov 7, 2007
  2. Jakub NarebskiNov 7, 2007
  3. Johannes SchindelinNov 8, 2007
  4. Junio C HamanoNov 8, 2007
  5. Johannes SchindelinNov 8, 2007
  6. Johannes SixtNov 8, 2007
  7. Junio C HamanoNov 8, 2007
  8. Andreas EricssonNov 8, 2007
  9. Jan HudecNov 15, 2007

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.