From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Florian Weimer <fw@deneb.enyo.de>,
"overseers@gcc.gnu.org" <overseers@gcc.gnu.org>,
Jonathan Wakely via Gcc <gcc@gcc.gnu.org>,
Overseers mailing list <overseers@sourceware.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Alexander Monakov <amonakov@ispras.ru>,
"Frank Ch. Eigler" <fche@elastic.org>,
"Frank Ch. Eigler" <fche@redhat.com>, Tom Tromey <tom@tromey.com>
Subject: Re: Not usable email content encoding
Date: Thu, 23 Apr 2020 10:39:38 +0200 [thread overview]
Message-ID: <20200423083938.GV2424@tucnak> (raw)
In-Reply-To: <CAH6eHdShSXwc4K7ar9HWgHu12tDQe-s2LifdvmVp8VytwYV-ew@mail.gmail.com>
On Thu, Apr 23, 2020 at 09:34:20AM +0100, Jonathan Wakely via Gcc wrote:
> I've been having problems with it recently, e.g.
> https://gcc.gnu.org/g:e76100ced607218a3bf had to fix a changelog,
> because https://gcc.gnu.org/g:d76925e46fad09fc9be67 put my changelog
> entry in the wrong place in gcc/testsuite/Changelog, as a result of a
> rebase using merge-changelog.
>
> Maybe we should follow glibc and get rid of ChangeLog files before
> trying to use automated CI and Git workflows.
I thought we are leaning towards generating the ChangeLog files from commit
messages rather than getting rid of them, but we need a reliable script to
find the ChangeLog snippet in the commit message and split it into the
separate ChangeLog files and reliable checker that will refuse commits with
badly formatted entries in there, because when it comes from commit
messages, we won't be able to fix mistakes in it later.
Jakub
next prev parent reply other threads:[~2020-04-23 8:39 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 13:45 Martin Liška
2020-03-16 13:47 ` Richard Earnshaw
2020-03-16 13:52 ` Martin Liška
2020-03-16 13:51 ` Florian Weimer
2020-03-16 13:52 ` Frank Ch. Eigler
2020-03-16 13:54 ` Alexander Monakov
2020-03-16 14:11 ` Martin Liška
2020-03-16 14:18 ` Jonathan Wakely
2020-03-17 19:46 ` Segher Boessenkool
2020-03-17 19:51 ` Frank Ch. Eigler
2020-03-17 21:45 ` Segher Boessenkool
2020-03-18 10:38 ` Florian Weimer
2020-03-18 11:01 ` Frank Ch. Eigler
2020-03-18 11:39 ` Florian Weimer
2020-03-18 14:19 ` Michael Matz
2020-03-18 14:22 ` Frank Ch. Eigler
2020-03-18 15:15 ` Bernd Schmidt
2020-03-18 16:22 ` Frank Ch. Eigler
2020-03-18 16:42 ` Michael Matz
2020-03-18 17:36 ` Christopher Faylor
2020-03-18 21:52 ` Jim Wilson
2020-03-18 22:29 ` Jonathan Wakely
2020-03-18 22:34 ` Jonathan Wakely
2020-03-18 22:44 ` Frank Ch. Eigler
2020-03-19 3:30 ` Christopher Faylor
2020-03-19 3:32 ` Christopher Faylor
2020-03-18 22:45 ` Joseph Myers
2020-03-18 23:02 ` Jonathan Wakely
2020-03-19 13:05 ` Tom Tromey
2020-03-19 13:26 ` Florian Weimer
2020-03-19 13:41 ` Richard Biener
2020-03-19 13:58 ` Florian Weimer
2020-03-19 18:17 ` Segher Boessenkool
2020-04-23 0:54 ` Tamar Christina
2020-04-23 5:47 ` Florian Weimer
2020-04-23 7:34 ` Richard Biener
2020-04-23 9:55 ` Tamar Christina
[not found] ` <CAH6eHdShSXwc4K7ar9HWgHu12tDQe-s2LifdvmVp8VytwYV-ew@mail.gmail.com>
2020-04-23 8:39 ` Jakub Jelinek [this message]
2020-04-23 15:32 ` Jeff Law
2020-04-23 11:46 ` Segher Boessenkool
[not found] ` <CAH6eHdTHsZWO9vuycKm22dDbSGSfzcrKbzEpb6vNdb-zXCiKjQ@mail.gmail.com>
2020-04-23 12:30 ` Segher Boessenkool
2020-04-23 15:33 ` Jeff Law
2020-04-23 16:57 ` Frank Ch. Eigler
2020-04-23 20:32 ` Segher Boessenkool
2020-04-23 20:27 ` Segher Boessenkool
2020-04-23 21:14 ` Tom Tromey
2020-04-24 15:48 ` Thomas Koenig
2020-04-24 17:09 ` Segher Boessenkool
2020-05-01 15:51 ` Jeff Law
2020-05-02 12:50 ` Segher Boessenkool
2020-03-19 18:08 ` Segher Boessenkool
2020-03-18 22:33 ` Frank Ch. Eigler
2020-03-19 0:17 ` Segher Boessenkool
2020-03-19 0:32 ` Segher Boessenkool
2020-04-06 20:58 ` Maciej W. Rozycki
2020-04-06 21:09 ` Frank Ch. Eigler
2020-04-06 21:59 ` Maciej W. Rozycki
[not found] ` <CAH6eHdTqJEM90d9+nNWrAa_zZrQQha79oMbnbVsRt_2Zd90PdA@mail.gmail.com>
2020-04-07 9:53 ` Florian Weimer
2020-04-08 12:38 ` Mark Wielaard
2020-04-08 13:50 ` Michael Matz
2020-04-08 21:15 ` Segher Boessenkool
2020-04-13 19:47 ` Christopher Faylor
2020-04-13 22:53 ` Michael Matz
2020-04-14 21:06 ` Christopher Faylor
2020-04-14 21:38 ` Maciej W. Rozycki
2020-04-15 2:59 ` Christopher Faylor
2020-04-07 15:13 ` Michael Matz
2020-04-07 15:22 ` Frank Ch. Eigler
2020-04-07 15:56 ` Michael Matz
2020-04-07 16:09 ` Christopher Faylor
2020-04-07 17:08 ` Maciej W. Rozycki
2020-04-09 18:19 ` Florian Weimer
2020-04-07 16:08 ` Christopher Faylor
2020-04-07 16:58 ` Maciej W. Rozycki
2020-04-06 23:15 ` Segher Boessenkool
2020-03-21 22:29 ` Maciej W. Rozycki
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=20200423083938.GV2424@tucnak \
--to=jakub@redhat.com \
--cc=amonakov@ispras.ru \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.org \
--cc=segher@kernel.crashing.org \
--cc=tom@tromey.com \
/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).