From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>,
Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org,
amodra@gmail.com, joern.rennecke@riscy-ip.com
Subject: Re: Using gcc/ChangeLog instead of gcc/testsuite/ChangeLog?
Date: Sat, 10 Aug 2019 17:06:00 -0000 [thread overview]
Message-ID: <20190810170629.GU31406@gate.crashing.org> (raw)
In-Reply-To: <20190810101246.GG2726@tucnak>
Hi!
On Sat, Aug 10, 2019 at 12:12:46PM +0200, Jakub Jelinek wrote:
> On Sat, Aug 10, 2019 at 08:53:45AM +0200, Hans-Peter Nilsson wrote:
> > Has there been a change of policy so it's a valid option to use
> > gcc/ChangeLog for testsuite changes? I was about to move a
> > semi-randomly spotted misplaced entry, and when checking if
> > there were others, I noticed that there's like tens of them, so
> > I thought better ask.
>
> Nothing in the policy changed. While we have mklog that helps with the job,
> it is still mostly hand written stuff and people make occassionally
> mistakes, that can happen to anyone. Admittedly some people repeat those
> mistakes often.
It's why I started doing those
gcc/testsuite/
things in the changelogs in the patches I send, to remind me what file
to apply what to. It helps :-)
> I ran the gcc/ subdirectory ChangeLogs through following script that doesn't
> seem to have false positives ATM and highlights some common mistakes people
> make and fixed them, see patch below.
Cool, thank you!
> Another common mistake is more than 2 newline characters in sequence.
Git goes as far as not allowing it in a log message (with standard
configurations, with the standard frontend tools). Drives me nuts, I
use it for formatting all the time.
Segher
prev parent reply other threads:[~2019-08-10 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 6:53 Hans-Peter Nilsson
2019-08-10 10:13 ` Jakub Jelinek
2019-08-10 17:06 ` Segher Boessenkool [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=20190810170629.GU31406@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=hans-peter.nilsson@axis.com \
--cc=jakub@redhat.com \
--cc=joern.rennecke@riscy-ip.com \
--cc=rguenther@suse.de \
/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).