From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: standardize a bit more the formatting of commit titles
Date: Wed, 16 Jan 2019 09:30:55 +0100 [thread overview]
Message-ID: <87muo1ovgg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181124101903.18138-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni's message of "Sat, 24 Nov 2018 11:19:03 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Currently, our commit titles are not very well standardized, and it
> would be great to standardize them a little bit more. A number of
> people use "<pkg>: " as prefix, others use "package/<pkg>: ". Some
> people start the rest of the commit title (after the prefix) with an
> upper-case letter, some with a lower-case letter.
> In an attempt to standardize this, this commit updates the manual with
> some examples of good commit titles.
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
We had some discussion if this is the best format to use, but it is
largely a matter of personal preferences, and having a documented
standard is better than none.
So committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-01-16 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 10:19 [Buildroot] [PATCH] docs/manual: standardize a bit more the formatting of commit titles Thomas Petazzoni
2018-11-25 1:16 ` Carlos Santos
2018-11-25 8:51 ` Peter Korsgaard
2018-11-25 8:56 ` Peter Korsgaard
2018-11-25 9:45 ` Thomas Petazzoni
2018-11-25 16:17 ` Yann E. MORIN
2018-11-25 20:09 ` Thomas Petazzoni
2018-11-26 20:20 ` Yann E. MORIN
2018-11-26 20:25 ` Thomas Petazzoni
2018-12-01 20:15 ` Yann E. MORIN
2019-01-16 8:30 ` Peter Korsgaard [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=87muo1ovgg.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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