{"thread":{"id":"36760","subject":"Best practices/conventions for tags and references in commit message","startedAt":"2014-05-27T11:26:35Z","lastAt":"2014-06-05T16:47:04Z","messageCount":4,"participants":["Thomas Koch","Johan Herland","Christian Couder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"242739","messageId":"201405271326.36031.thomas@koch.ro","threadId":"36760","inReplyTo":null,"subject":"Best practices/conventions for tags and references in commit message","fromName":"Thomas Koch","fromEmail":"thomas@koch.ro","sentAt":"2014-05-27T11:26:35Z","receivedAt":"2014-05-27T11:26:35Z","isPatch":false,"sender":{"key":"thomas@koch.ro","avatar":null},"body":"Hi,\n\ndifferent projects or tools have conventions to include machine parsable \ninformation in commit messages, e.g.:\n\nCloses: #42\nThanks: my mother, my wife\nGit-Dch: Ignore\nCommit-Id: 50M3R34LLYR4ND0MB1TSANDNUMB3R5\n\n(see thread: \"RFE: support change-id generation natively\" for Commit-Id)\n(\"Git-Dch: Ignore\" ecludes the commit from the changelog)\n\nAre you aware of any convention or best practices for such tags that are used \nin more than one project? Are there more tags like these?\n\nMaybe it would also be helpful to have some more plumbing support from Git for \nsuch tags. But I've not yet thought enough about this.\n\nBest regards, Thomas Koch\n"},{"id":"242743","messageId":"CALKQrgfYfXyXs0K+tq6xXNaQ-J1VdwJ7iodyE3s8X8wHN8WuvA@mail.gmail.com","threadId":"36760","inReplyTo":"201405271326.36031.thomas@koch.ro","subject":"Re: Best practices/conventions for tags and references in commit message","fromName":"Johan Herland","fromEmail":"johan@herland.net","sentAt":"2014-05-27T13:49:24Z","receivedAt":"2014-05-27T13:49:24Z","isPatch":false,"sender":{"key":"johan@herland.net","avatar":"https://avatars.githubusercontent.com/u/547031?v=4"},"body":"Search the mailing list archives for git-interpret-trailers. It's coming. :)\n\n\n...Johan\n\nOn Tue, May 27, 2014 at 1:26 PM, Thomas Koch wrote:\n> Hi,\n>\n> different projects or tools have conventions to include machine parsable\n> information in commit messages, e.g.:\n>\n> Closes: #42\n> Thanks: my mother, my wife\n> Git-Dch: Ignore\n> Commit-Id: 50M3R34LLYR4ND0MB1TSANDNUMB3R5\n>\n> (see thread: \"RFE: support change-id generation natively\" for Commit-Id)\n> (\"Git-Dch: Ignore\" ecludes the commit from the changelog)\n>\n> Are you aware of any convention or best practices for such tags that are used\n> in more than one project? Are there more tags like these?\n>\n> Maybe it would also be helpful to have some more plumbing support from Git for\n> such tags. But I've not yet thought enough about this.\n>\n> Best regards, Thomas Koch\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n\n\n\n-- \nJohan Herland, \nwww.herland.net\n"},{"id":"243395","messageId":"201406051610.41373.thomas@koch.ro","threadId":"36760","inReplyTo":"CALKQrgfYfXyXs0K+tq6xXNaQ-J1VdwJ7iodyE3s8X8wHN8WuvA@mail.gmail.com","subject":"Re: Best practices/conventions for tags and references in commit message","fromName":"Thomas Koch","fromEmail":"thomas@koch.ro","sentAt":"2014-06-05T14:10:40Z","receivedAt":"2014-06-05T14:10:40Z","isPatch":false,"sender":{"key":"thomas@koch.ro","avatar":null},"body":"On Tuesday, May 27, 2014 03:49:24 PM Johan Herland wrote:\n> Search the mailing list archives for git-interpret-trailers. It's coming.\nNice!\n\nI started a table to collect how different projects or tools use trailers:\nhttps://git.wiki.kernel.org/index.php/CommitMessageConventions#Trailers\n\nIt would be nice to see more examples and in the long run to have some best \npractices recommended by gits documentation and supported across different bug \ntrackers, changelog generators, statistic generators, repository viewers, \netc..\n\nRegards,\n\nThomas Koch\n"},{"id":"243406","messageId":"CAP8UFD3MQ_BEyZFL2oE=KCGnZrCW5-NzXnVaaAg_6HMBAN-8hA@mail.gmail.com","threadId":"36760","inReplyTo":"201406051610.41373.thomas@koch.ro","subject":"Re: Best practices/conventions for tags and references in commit message","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2014-06-05T16:47:04Z","receivedAt":"2014-06-05T16:47:04Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Thu, Jun 5, 2014 at 4:10 PM, Thomas Koch wrote:\n> On Tuesday, May 27, 2014 03:49:24 PM Johan Herland wrote:\n>> Search the mailing list archives for git-interpret-trailers. It's coming.\n> Nice!\n>\n> I started a table to collect how different projects or tools use trailers:\n> https://git.wiki.kernel.org/index.php/CommitMessageConventions#Trailers\n\nGreat!\n\nIt would be even better if you could add links to one or more actual\ncommits that contain the specified trailer.\n\nFor example for openstack, it would be nice to have real examples of\nDocImpact, SecurityImpact and UpgradeImpact.\n\n> It would be nice to see more examples and in the long run to have some best\n> practices recommended by gits documentation and supported across different bug\n> trackers, changelog generators, statistic generators, repository viewers,\n> etc..\n\nYeah, what is also interesting is that some people/projects/tools use\nthings that are in some ways trailer like. For example GitHub parses\ncommit messages for things like \"fix #1234\" and there are also people\nadding refs at the end of commit messages like:\n\n[1] http://www.example.com/example_ref.html\n\nThanks,\nChristian.\n"}]}