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

Re: "git tag --contains <id>" is too chatty, if <id> is invalid

From
Jeff King <peff@peff.net>
Date
Mar 19, 2016, 18:12 UTC
Message-ID
<20160319181228.GA9115@sigill.intra.peff.net>
In-Reply-To
<CAJj6+1HaVnRcmDHOTDdx=o8a+aXvSi8+LykWzrfx7knE-_3ocg@mail.gmail.com>
On Sat, Mar 19, 2016 at 11:38:09PM +0530, Chirayu Desai wrote:
Show 5 quoted lines
> > You'd teach parse_opt_commits() to store the string _name_ of the
> > argument (e.g., using a string_list rather than a commit_list), and then
> > later resolve those names into commits.
> Gotcha, will need to figure out where exactly would those names be
> resolved, can do after following the code path a bit more, can do.

Without looking too closely, I suspect you could do it as the first step in filter_refs(). Or alternatively, add a function to "finalize" the filter state before making queries of it.

-Peff
Previous: Chirayu DesaiNext: Chirayu Desai
Message 6 of 10 in “Re: "git tag --contains <id>" is too chatty, if <id> is invalid”
  1. Chirayu DesaiMar 19, 2016
  2. Pranit BauvaMar 19, 2016
  3. Chirayu DesaiMar 19, 2016
  4. Jeff KingMar 19, 2016
  5. Chirayu DesaiMar 19, 2016
  6. Jeff KingMar 19, 2016
  7. Chirayu DesaiMar 20, 2016
  8. Jeff KingMar 23, 2016
  9. Chirayu DesaiMar 24, 2016
  10. Junio C HamanoMar 20, 2016

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.