From: Michael Schubert <mschub@elegosoft.com>
To: Joseph Huttner <huttnified@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to make devs write better commit messages
Date: Wed, 07 Dec 2011 00:18:58 +0100 [thread overview]
Message-ID: <4EDEA2E2.3030002@elegosoft.com> (raw)
In-Reply-To: <CAOJsP-X0ZWT5HLHcBc2FmhoMpWFOvEFADiM9jGZ9R1ctqHDJ9w@mail.gmail.com>
On 12/06/2011 11:55 PM, Joseph Huttner wrote:
> So I know that there is a somewhat standard format of commit messages
> in Git, which Linus outlines here:
>
> https://github.com/torvalds/subsurface/blob/master/README#L164
>
> Trouble is, when most people go to commit, the file that the editor
> opens has no reminder of how to write a proper commit message. Often
> I find myself having to go back through the commit log, or consulting
> the above link.
>
> I propose two things:
>
> 1. An optional flag in the Git config that, if set, shows the format
> of a typical commit message in your commit message template.
>
> 2. The ability to modify this commit message template. Many teams
> use automated tools to read commit messages and then do automated
> tasks based on that data, like comment an RT ticket. Thus, developers
> need to be reminded of these team-specific settings as well.
>
> What are your thoughts?
If it's no social issue but just due to lack of a reminder you
could provide a template for commit.template. Either way: you
still would have to force people to set it.?
next prev parent reply other threads:[~2011-12-06 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 22:55 How to make devs write better commit messages Joseph Huttner
2011-12-06 23:18 ` Michael Schubert [this message]
2011-12-07 2:28 ` Junio C Hamano
2011-12-07 0:08 ` Hilco Wijbenga
2011-12-07 7:06 ` Thomas Koch
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=4EDEA2E2.3030002@elegosoft.com \
--to=mschub@elegosoft.com \
--cc=git@vger.kernel.org \
--cc=huttnified@gmail.com \
/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).