From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Commit messages becoming too short
Date: Tue, 05 Mar 2013 17:19:13 +0000 [thread overview]
Message-ID: <1362503953.11727.27.camel@ted> (raw)
There appears to be a general trend towards short commit messages. I
don't impose a "must have a long log and short log" policy but I'll have
to if things don't improve.
To be clear, the commit message needs to say not just what changed but
*why* the change is necessary, e.g. what error it causes without it.
Commit messages need to stand alone without reference to any linked
bugzilla entry either, that is just there as a way to further look at
the issue.
I'm going to be getting stricter about this.
Cheers,
Richard
reply other threads:[~2013-03-05 17:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1362503953.11727.27.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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