From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc@gcc.gnu.org
Subject: More consistency for Git log messages?
Date: Tue, 29 Dec 2020 00:54:53 +0100 (CET) [thread overview]
Message-ID: <43eb3d64-2d5d-cbc9-3e3e-e06eedc2704b@pfeifer.com> (raw)
Having spent a bit more time with GCC sources (as opposed to wwwdocs)
recently and looking for prior art to guide me, I noticed there's a
lot of options to specific the ChangeLog file(s) to use.
And correspondingly a lot of inconsistency.
Right now we seem to allow for
1. gcc/cp/ChangeLog
2. gcc/cp/ChangeLog:
3. gcc/cp
4. gcc/cp:
5. gcc/cp/
and probably more.
Can we streamline this a bit and converge on one of the forms 3-5?
Personally I'd suggest 3 (the shortest) or 5 (the directory), but whatever
... as long as things become more consistent, which is easier on newbies
and reading logs (or automatically processing them later on).
Gerald
next reply other threads:[~2020-12-28 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 23:54 Gerald Pfeifer [this message]
2020-12-29 8:49 ` Jonathan Wakely
2020-12-30 21:34 ` Martin Sebor
2020-12-30 14:19 ` Segher Boessenkool
2020-12-30 14:25 ` H.J. Lu
2020-12-30 14:49 ` Jakub Jelinek
2021-01-06 8:23 ` Martin Liška
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=43eb3d64-2d5d-cbc9-3e3e-e06eedc2704b@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).