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

Re: [PATCH] bisect: Store first bad commit as comment in log file

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 15, 2013, 15:00 UTC
Message-ID
<7vwqs3zvmu.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130415095339.GA28480@pvv.ntnu.no>
Torstein Hegge <hegge@resisty.net> writes:
> I was wondering why "git grep show-ref *.sh" gave so few users. It looks
> like rev-parse is more common.

It is primarily because show-ref is slightly newer. When you have a full refname (e.g. refs/bisect/bad) and not an arbitrary object name that is spelled in a random way (e.g. master~24):

       show-ref --verify refs/bisect/bad
is a perfectly valid way to make sure it _is_ an existing ref.
Cf. 358ddb62cfd0 (Add "git show-ref" builtin command, 2006-09-15)
Previous: Torstein HeggeNext: Torstein Hegge
Message 4 of 11 in “bisect: Store first bad commit as comment in log file”
  1. bisect: Store first bad commit as comment in log fileTorstein Hegge, Apr 13, 2013
  2. Christian CouderApr 15, 2013
  3. Torstein HeggeApr 15, 2013
  4. Junio C HamanoApr 15, 2013
  5. Torstein HeggeApr 22, 2013
  6. Junio C HamanoApr 22, 2013
  7. Torstein HeggeApr 22, 2013
  8. Junio C HamanoApr 22, 2013
  9. Christian CouderApr 25, 2013
  10. bisect: Fix log output for multi-parent skip rangesTorstein Hegge, May 22, 2013
  11. Junio C HamanoApr 15, 2013

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.