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

Re: [PATCH] fsck: do not crash on tag objects which do not contain an empty line

From
APAndy Parkins <andyparkins@gmail.com>
Date
Jun 8, 2007, 08:32 UTC
Message-ID
<200706080932.05098.andyparkins@gmail.com>
In-Reply-To
<Pine.LNX.4.64.0706072338260.4046@racer.site>
On Thursday 2007 June 07, Johannes Schindelin wrote:
> +		error("tag %s does not contain any tag?", refname);
Seems a bad error message to me.  Also, why is it a question?
 git: tag does not contain a tag
 user: WTF?
Perhaps, "The annotated tag, %s, does not contain a message", or similar?

Also - is this really something that should be complained about? I'm wondering why it is important that tag objects contain a message? For example, tagging a release as v1.0.0 - it's important to record who tagged it, and when it was tagged, but I can certainly envisage there not being a message to go with it. Most tags in the git repository are just a repeat of the tag name in the message.

Andy
-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
Previous: Johannes Schindelin
Message 10 of 10 in “fsck: do not crash on tag objects which do not contain an empty line”
  1. fsck: do not crash on tag objects which do not contain an empty lineJohannes Schindelin, Jun 7, 2007
  2. Johan HerlandJun 7, 2007
  3. Johannes SchindelinJun 7, 2007
  4. Johan HerlandJun 7, 2007
  5. Johannes SchindelinJun 7, 2007
  6. Nicolas PitreJun 8, 2007
  7. Johan HerlandJun 8, 2007
  8. Junio C HamanoJun 8, 2007
  9. Johannes SchindelinJun 8, 2007
  10. Andy ParkinsJun 8, 2007

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.