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

Re: git tag: don't complain of empty messages

From
Han-Wen Nienhuys <hanwen@xs4all.nl>
Date
Nov 16, 2006, 00:14 UTC
Message-ID
<455BAD80.1080108@xs4all.nl>
In-Reply-To
<7v64dgo9gj.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano escreveu:
> I do not have a strong objection against allowing tags without
> messages, but at the same time I do not see a compelling reason
> to allow them either.  Care to explain what workflow is helped
> by an empty tag?

the tagname usually is enough of a description, but I want the tags to end up in the object DB, eg.:

   git tag release/2.10.0 HEAD
now I have to use
   git tag -m "this really sucks"  release/2.10.0 HEAD
Previous: Junio C HamanoNext: Jakub Narebski
Message 6 of 10 in “git tag: don't complain of empty messages”
  1. Han-Wen NienhuysNov 15, 2006
  2. Johannes SchindelinNov 15, 2006
  3. Han-Wen NienhuysNov 15, 2006
  4. Johannes SchindelinNov 15, 2006
  5. Junio C HamanoNov 15, 2006
  6. Han-Wen NienhuysNov 16, 2006
  7. Jakub NarebskiNov 16, 2006
  8. Han-Wen NienhuysNov 16, 2006
  9. Han-Wen NienhuysNov 26, 2006
  10. Han-Wen NienhuysNov 26, 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.