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

Re: [PATCH] gitk: parse arbitrary commit-ish in SHA1 field

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 11, 2009, 05:13 UTC
Message-ID
<7vtz0fndak.fsf@alter.siamese.dyndns.org>
In-Reply-To
<f7e6f82a33aa8496de81262d641953534089e980.1249742874.git.trast@student.ethz.ch>
Thomas Rast <trast@student.ethz.ch> writes:
> +	} else {
> +	    if {[catch {set id [exec git rev-parse $sha1string]}]} {

"--verify", or "--no-flags --revs-only"? Examples of possible bad input strings that you may otherwise not catch are:

	master..
        --merge -- a
Previous: Thomas RastNext: Thomas Rast
Message 2 of 4 in “gitk: parse arbitrary commit-ish in SHA1 field”
  1. gitk: parse arbitrary commit-ish in SHA1 fieldThomas Rast, Aug 8, 2009
  2. Junio C HamanoAug 11, 2009
  3. gitk: parse arbitrary commit-ish in SHA1 fieldThomas Rast, Aug 13, 2009
  4. Paul MackerrasAug 13, 2009

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.