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

Re: commit type

From
7rans <transfire@gmail.com>
Date
Oct 31, 2008, 19:20 UTC
Message-ID
<loom.20081031T191102-81@post.gmane.org>
In-Reply-To
<ee77f5c20810311104m6044bf70r1d9d405fa04454e0@mail.gmail.com>
David Symonds <dsymonds <at> gmail.com> writes:
Show 8 quoted lines
> 
> On Fri, Oct 31, 2008 at 10:58 AM, 7rans <transfire <at> gmail.com> wrote:
> 
> > Currently I achieve this by adding "[type]" to the end of my commit messages.
> > But of course that's less than optimal.
> 
> Why is that less than optimal? It seems a lot less intrusive than what
> you suggest.

Because it becomes formalized. Which means people can write tools other people can use to work with them.

Having the type embedded in commit message not only clutters up the commit messages, but different people would do it differently, using different brackets or putting it the start or the end of the message, etc.

And of course it would be easier to ask git to list certain types of commits if it knew about them.

7rans.
Previous: Samuel Lucas Vaz de MelloNext: Johannes Schindelin
Message 4 of 8 in “commit type”
  1. 7ransOct 31, 2008
  2. David SymondsOct 31, 2008
  3. Samuel Lucas Vaz de MelloOct 31, 2008
  4. 7ransOct 31, 2008
  5. Johannes SchindelinOct 31, 2008
  6. 7ransNov 1, 2008
  7. bd_Nov 2, 2008
  8. 7ransNov 3, 2008

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.