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

Re: [PATCH] tag -d: print sha1 of deleted tag

From
Jari Aalto <jari.aalto@cante.net>
Date
Dec 10, 2009, 13:16 UTC
Message-ID
<87hbrz6kbs.fsf@jondo.cante.net>
In-Reply-To
<20091210124929.GA444@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 9 quoted lines
> On Thu, Dec 10, 2009 at 01:23:43PM +0100, Michael J Gruber wrote:
>
>> Print the sha1 of the deleted tag (in addition to the tag name) so that
>> one can easily recreate a mistakenly deleted tag:
>> 
>> git tag -d tagname
>> Deleted tag 'tagname' DEADBEEF
>> git tag 'tagname' DEADBEEF # for lightweight tags
>> git update-ref refs/tags/'tagname' DEADBEEF # for annotated tags
> That being said, I am not a fan of the cut-and-paste format. This is not
> something that happens so frequently
It dpends on user. For me it it does.
Show 5 quoted lines
>   1. It is not immediately obvious to a user seeing this message
>      for this first time exactly what the trailing sha1 means.
>
>   2. Even if they know what it means, it is not immediately obvious that
>      the error line is meant to be cut-and-pasted.

"not meant" specifically, but it's very convenient to have it in format that happens to be "cut-n-paste ready". The SHA itself is easily understood in the context.

Thanks for all that have so quickly implemented this, Jari

Previous: Jeff KingNext: Michael J Gruber
Message 6 of 10 in “FEATURE REQUEST: display <commit SHA> in message: git tag -d”
  1. Jari AaltoDec 10, 2009
  2. tag -d: print sha1 of deleted tagMichael J Gruber, Dec 10, 2009
  3. Björn SteinbrinkDec 10, 2009
  4. Michael J GruberDec 10, 2009
  5. Jeff KingDec 10, 2009
  6. Jari AaltoDec 10, 2009
  7. Michael J GruberDec 10, 2009
  8. Jeff KingDec 10, 2009
  9. tag -d: print sha1 of deleted tagMichael J Gruber, Dec 10, 2009
  10. Zoltán FüzesiDec 10, 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.