From: Tobias Burnus <burnus@net-b.de>
To: Jerry DeLisle <jvdelisle@charter.net>, fortran@gcc.gnu.org
Subject: Re: Question on push
Date: Sat, 16 Jan 2021 14:00:33 +0100 [thread overview]
Message-ID: <b5e62469-4986-4e40-e3f1-781aaf64986b@net-b.de> (raw)
In-Reply-To: <fb2c396c-3cfe-9575-9b50-8f4e98b5da7e@charter.net>
Hi Jerry,
yes, ChangeLog files are automatically generated from the commit log by
the contrib/gcc-changelog/. If the generated changelog file is wrong
because the script mishandled something, that script should be fixed.
In any case, if the ChangeLog file is wrong, you have to wait until the
nightly script has run (which also bumps the gcc/DATESTAMP) and then you
can fix the ChangeLog files and commit them.
Tobias
PS: Your commit also missed the PR in the commit.
PPS: If you backport something, use 'git cherry-pick -x', which also
will handle the backported information in the changelog.
On 15.01.21 23:36, Jerry DeLisle wrote:
> Naturally the push was rejected several times. As I was trying to
> interpret the reasons given and go back and read the instructions, I
> was given the impression that the behind the scenes process would
> ammend the actual ChangeLog files for you. I have not seen this
> happen so to clarify, There are two ChangeLog files involved.
> gcc/testsuite/ChangeLog and libgfortran/ChangeLog.
prev parent reply other threads:[~2021-01-16 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 22:36 Jerry DeLisle
2021-01-16 10:23 ` Thomas Koenig
2021-01-16 13:00 ` Tobias Burnus [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=b5e62469-4986-4e40-e3f1-781aaf64986b@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=jvdelisle@charter.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).