From: Jeff Law <law@redhat.com>
To: "Martin Liška" <mliska@suse.cz>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 0/3] mklog improvements
Date: Wed, 04 Sep 2019 14:56:00 -0000 [thread overview]
Message-ID: <02c2c05a-1df5-18d3-02fc-9ae3fdeb9bb2@redhat.com> (raw)
In-Reply-To: <82232669-1f90-ca59-d7a0-7354a9388b99@suse.cz>
On 9/4/19 2:05 AM, Martin Liška wrote:
> On 9/3/19 6:37 PM, Jeff Law wrote:
>> On 8/30/19 2:55 AM, Martin Liška wrote:
>>> PING^1
>>>
>>> On 8/13/19 9:49 AM, Martin Liska wrote:
>>>> Hi.
>>>>
>>>> I'm sending format independent changes to mklog that should
>>>> improve the script. It addresses couple of improvement
>>>> mentioned here:
>>>> https://gcc.gnu.org/ml/gcc-patches/2019-08/msg00031.html
>>>>
>>>> Martin
>>>>
>>>> Martin Liska (3):
>>>> Â Â Use argparse.ArgumentParser for mklog.
>>>> Â Â mklog: parse PR references from new test files
>>>> Â Â mklog: Do not print changed functions in testsuite
>> So there's a ton of follow-ups (primarily between Jakub and yourself).
>
> Yes, the follow up is about possible change to ChangeLog format. I first
> provided a patch, but later I realized that I would rather stick with
> the current format.
I'd rather drop ChangeLogs and generate them from the VCS, but that's
another discussion entirely :-)
>
>>
>> What's the state of the changes Jakub has requested? Can we go forward
>> with the patch as-is and iterate on further improvements?
>
> Yes, I'm going to install these 3 patches which do not change the format.
THat works for me.
jeff
prev parent reply other threads:[~2019-09-04 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 7:51 Martin Liska
2019-08-13 7:51 ` [PATCH 3/3] mklog: Do not print changed functions in testsuite Martin Liska
2019-08-13 7:57 ` [PATCH 2/3] mklog: parse PR references from new test files Martin Liska
2019-08-13 8:18 ` [PATCH 1/3] Use argparse.ArgumentParser for mklog Martin Liska
2019-08-30 9:24 ` [PATCH 0/3] mklog improvements Martin Liška
2019-09-03 16:37 ` Jeff Law
2019-09-04 8:05 ` Martin Liška
2019-09-04 14:56 ` Jeff Law [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=02c2c05a-1df5-18d3-02fc-9ae3fdeb9bb2@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).