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

Re: [PATCH] sha1_name: accept output of git-describe

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 20, 2006, 21:31 UTC
Message-ID
<Pine.LNX.4.63.0609202330190.19042@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<7v64figrhu.fsf@assigned-by-dhcp.cox.net>
Hi,
On Wed, 20 Sep 2006, Junio C Hamano wrote:
> Shouldn't you also verify the leading ref (most likely a tag)
> exists (and optionally check that it precedes the commit you
> decoded into, but that is probably more expensive than it's
> worth)?

I debated this with myself. But there is the cost, and more importantly the possibility that your victim^H^H^H^H^H^Hother side does not have the tag at all (for whatever reasons).

Ciao, Dscho

Previous: Junio C HamanoNext: Shawn Pearce
Message 3 of 4 in “sha1_name: accept output of git-describe”
  1. sha1_name: accept output of git-describeJohannes Schindelin, Sep 20, 2006
  2. Junio C HamanoSep 20, 2006
  3. Johannes SchindelinSep 20, 2006
  4. Shawn PearceSep 20, 2006

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.