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

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

From
Jeff King <peff@peff.net>
Date
Dec 10, 2009, 13:36 UTC
Message-ID
<20091210133645.GA2149@coredump.intra.peff.net>
In-Reply-To
<4B20F733.6010401@drmicha.warpmail.net>
On Thu, Dec 10, 2009 at 02:27:15PM +0100, Michael J Gruber wrote:
Show 6 quoted lines
> >   1. It is not immediately obvious to a user seeing this message
> >      for this first time exactly what the trailing sha1 means. We
> >      already had this discussion with "git branch -d" and decided
> >      that "(was DEADBEEF)" was more readable.
> 
> So, should we simply go with that then?

I think so. Jari obviously disagrees, but I don't have much more to say in favor of it except that I find the other ugly and unintuitive. So it is up to you what you want to submit and Junio what he wants to apply. :)

> Meanwhile, RFCs/PATCHes crossed paths. I take it that Zoltan suggests
> giving the same output for force-overwritten existing tags. I beat him
> by 11 minutes, though ;)

Yes, I think if you are going to protect "tag -d", you might as well protect overwriting, as well. Which made me think at first that we need something similar for "branch -f", but I don't think we do; the last branch value will be left in the reflog (but with tags, there is no reflog).

-Peff
Previous: Michael J GruberNext: Michael J Gruber
Message 8 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.