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

Re: Best practices/conventions for tags and references in commit message

From
TKThomas Koch <thomas@koch.ro>
Date
Jun 5, 2014, 14:10 UTC
Message-ID
<201406051610.41373.thomas@koch.ro>
In-Reply-To
<CALKQrgfYfXyXs0K+tq6xXNaQ-J1VdwJ7iodyE3s8X8wHN8WuvA@mail.gmail.com>
On Tuesday, May 27, 2014 03:49:24 PM Johan Herland wrote:
> Search the mailing list archives for git-interpret-trailers. It's coming.
Nice!

I started a table to collect how different projects or tools use trailers: https://git.wiki.kernel.org/index.php/CommitMessageConventions#Trailers

It would be nice to see more examples and in the long run to have some best practices recommended by gits documentation and supported across different bug trackers, changelog generators, statistic generators, repository viewers, etc..

Regards,
Thomas Koch
Previous: Johan HerlandNext: Christian Couder
Message 3 of 4 in “Best practices/conventions for tags and references in commit message”
  1. Thomas KochMay 27, 2014
  2. Johan HerlandMay 27, 2014
  3. Thomas KochJun 5, 2014
  4. Christian CouderJun 5, 2014

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.