From: Christian Couder <christian.couder@gmail.com>
To: Thomas Koch <thomas@koch.ro>
Cc: Johan Herland <johan@herland.net>,
Git mailing list <git@vger.kernel.org>
Subject: Re: Best practices/conventions for tags and references in commit message
Date: Thu, 5 Jun 2014 18:47:04 +0200 [thread overview]
Message-ID: <CAP8UFD3MQ_BEyZFL2oE=KCGnZrCW5-NzXnVaaAg_6HMBAN-8hA@mail.gmail.com> (raw)
In-Reply-To: <201406051610.41373.thomas@koch.ro>
On Thu, Jun 5, 2014 at 4:10 PM, Thomas Koch <thomas@koch.ro> wrote:
> 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
Great!
It would be even better if you could add links to one or more actual
commits that contain the specified trailer.
For example for openstack, it would be nice to have real examples of
DocImpact, SecurityImpact and UpgradeImpact.
> 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..
Yeah, what is also interesting is that some people/projects/tools use
things that are in some ways trailer like. For example GitHub parses
commit messages for things like "fix #1234" and there are also people
adding refs at the end of commit messages like:
[1] http://www.example.com/example_ref.html
Thanks,
Christian.
prev parent reply other threads:[~2014-06-05 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 11:26 Best practices/conventions for tags and references in commit message Thomas Koch
2014-05-27 13:49 ` Johan Herland
2014-06-05 14:10 ` Thomas Koch
2014-06-05 16:47 ` Christian Couder [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD3MQ_BEyZFL2oE=KCGnZrCW5-NzXnVaaAg_6HMBAN-8hA@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=thomas@koch.ro \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).