From: Martin Sebor <msebor@gmail.com>
To: Tobias Burnus <tobias@codesourcery.com>,
Jonathan Wakely <jwakely@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
gcc Mailing List <gcc@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [Patch] contrib/mklog.py: Improve PR handling
Date: Fri, 18 Jun 2021 10:40:40 -0600 [thread overview]
Message-ID: <01eeb5be-809a-182f-fafa-9c3542ea29f8@gmail.com> (raw)
In-Reply-To: <3eaccd30-3c1d-8f62-6382-e3ceb1b4bad2@codesourcery.com>
On 6/18/21 5:25 AM, Tobias Burnus wrote:
> On 18.06.21 13:10, Jonathan Wakely wrote:
>
>> On Fri, 18 Jun 2021 at 12:05, Tobias Burnus wrote:
>>> PR c++/12394 - internal compiler error: in write_type, at
>>> cp/mangle.c:1517
>>> PR fortran/100123 - -ftree-fre gives incorrect result in subroutine
>>> with array declared as length 1
>>> PR c++/12394
>>> PR fortran/100123
>> Now that we put these PR cmpt/nnnn lines before the xxx/ChangeLog
>> entries, is there any reason to indent them with a TAB?
>
> My understanding with the PR before vs. after the xxx/ChangeLog is
> that if you put them before, they apply to all changelog entries
> and if you put them afterward, it only only applies to the those
> ChangeLog files for which they have been mentioned.
>
> (But I also might have misread the code/were misguided by the
> var names.)
>
> And when manually creating the changelog from scratch, they still
> often end up after the ChangeLog line.
>
> But otherwise, I am not attached to the tab. Just one thing:
> It might be slightly inconsistent to require the tab after the
> xxx/ChangeLog line but not before that line. And I think a
> tab should be used after the xxx/ChangeLog line.
>
>> If we didn't require the TAB before them, then the lines added by -p
>> would serve the same purpose, and we wouldn't need to repeat them
>>
>> So instead of requiring "^\tPR .*/\d+$" for the PR entry, require
>> "^\t?PR ([^/]+)/\d+"
> I think we should require either ($|\s) after the PR number but
> otherwise, it works for me.
>
> I am sure that Martin Sebor will like this change as he currently
> writes changelogs (see in this thread or) like the following one.
I do like adding the bug title and extracting the component from
Bugzilla. IIRC, Martin Liska implemented -p in mklog.py on my
request (although I just discovered the option recently). I was
going to propose something similar to your solution:
https://gcc.gnu.org/pipermail/gcc/2021-June/236460.html
but I'm happy to let you run with it.
Thanks
Martin
>
> In that sense, there would be a precedent in terms of actual usage.
>
> ----------
> Teach compute_objsize about placement new [PR100876].
>
> Resolves:
> PR c++/100876 - -Wmismatched-new-delete should understand placement new
> when it's not inlined
>
> gcc/ChangeLog:
>
> PR c++/100876
> ----------
>
> Tobias
>
> PS: My feeling is that you like the proposed mklog patch :-)
>
> -----------------
> Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München
> Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung,
> Frank Thürauf
next prev parent reply other threads:[~2021-06-18 16:40 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4c1114a7-2377-99e4-d451-1a086857e991@linux.ibm.com>
2021-06-10 5:22 ` git gcc-commit-mklog doesn't extract PR number to ChangeLog Xionghu Luo
2021-06-10 6:17 ` Martin Liška
2021-06-10 6:25 ` Xionghu Luo
2021-06-10 8:07 ` Martin Liška
2021-06-10 6:35 ` Tobias Burnus
2021-06-10 8:07 ` Martin Liška
2021-06-10 9:44 ` Jonathan Wakely
2021-06-10 10:01 ` Jonathan Wakely
2021-06-10 10:08 ` Jakub Jelinek
2021-06-10 10:40 ` Jonathan Wakely
2021-06-10 14:55 ` Martin Sebor
2021-06-10 15:54 ` Tobias Burnus
2021-06-10 16:05 ` Jonathan Wakely
2021-06-10 15:56 ` Jonathan Wakely
2021-06-10 17:06 ` Martin Sebor
2021-06-10 17:20 ` Martin Sebor
2021-06-10 17:30 ` Jakub Jelinek
2021-06-10 18:55 ` Martin Sebor
2021-06-10 19:09 ` Jakub Jelinek
2021-06-10 21:16 ` Martin Sebor
2021-06-10 21:28 ` Jakub Jelinek
2021-06-10 21:56 ` Martin Sebor
2021-06-11 9:13 ` Jonathan Wakely
2021-06-11 17:02 ` Martin Sebor
2021-06-11 17:05 ` Jakub Jelinek
2021-06-11 17:32 ` Jonathan Wakely
2021-06-11 18:01 ` Martin Sebor
2021-06-11 18:14 ` Jonathan Wakely
2021-06-16 0:56 ` Hans-Peter Nilsson
2021-06-16 2:03 ` Martin Sebor
2021-06-16 3:42 ` Jason Merrill
2021-06-16 14:31 ` Martin Sebor
2021-06-16 20:49 ` Jason Merrill
2021-06-16 21:45 ` Martin Sebor
2021-06-16 23:45 ` Jason Merrill
2021-06-17 0:17 ` Martin Sebor
2021-06-17 0:40 ` Jason Merrill
2021-06-17 1:01 ` Martin Sebor
2021-06-17 1:46 ` Jason Merrill
2021-06-17 10:18 ` Jonathan Wakely
2021-06-17 14:55 ` Martin Sebor
2021-06-17 15:11 ` Michael Matz
2021-06-17 15:33 ` Martin Sebor
2021-06-17 16:31 ` Jakub Jelinek
2021-06-17 16:32 ` Jonathan Wakely
2021-06-17 18:00 ` Martin Sebor
2021-06-17 10:08 ` Richard Earnshaw
2021-06-17 17:12 ` Joseph Myers
2021-06-17 17:21 ` Jason Merrill
2021-06-17 17:21 ` Jakub Jelinek
2021-06-18 9:32 ` Richard Earnshaw
2021-06-18 11:05 ` [Patch] contrib/mklog.py: Improve PR handling (was: git gcc-commit-mklog doesn't extract PR number to ChangeLog) Tobias Burnus
2021-06-18 11:10 ` Jonathan Wakely
2021-06-18 11:24 ` Jakub Jelinek
2021-06-18 11:25 ` Tobias Burnus
2021-06-18 11:40 ` Jonathan Wakely
2021-06-21 7:28 ` Martin Liška
2021-06-18 16:40 ` Martin Sebor [this message]
2021-06-18 14:41 ` Jason Merrill
2021-06-18 16:47 ` [Patch] contrib/mklog.py: Improve PR handling Martin Sebor
2021-06-18 16:59 ` Iain Sandoe
2021-06-21 6:42 ` [Patch] contrib/mklog.py: Improve PR handling (was: git gcc-commit-mklog doesn't extract PR number to ChangeLog) Tobias Burnus
2021-06-21 7:26 ` Martin Liška
2021-06-21 8:02 ` Iain Sandoe
2021-06-21 7:54 ` [Patch, v2] contrib/mklog.py: Improve PR handling (was: " Tobias Burnus
2021-06-21 8:09 ` Martin Liška
2021-06-21 8:37 ` Tobias Burnus
2021-06-21 12:53 ` Martin Liška
2021-06-21 13:26 ` Tobias Burnus
2021-06-22 7:30 ` [RFC][PATCH] contrib: add git-commit-mklog wrapper Martin Liška
2021-06-22 8:23 ` Tobias Burnus
2021-06-22 8:31 ` Martin Liška
2021-06-22 18:40 ` Jason Merrill
2021-06-23 7:40 ` Martin Liška
2021-06-16 13:46 ` git gcc-commit-mklog doesn't extract PR number to ChangeLog Jonathan Wakely
2021-06-16 17:44 ` Hans-Peter Nilsson
2021-06-11 9:08 ` Jonathan Wakely
2021-06-11 9:35 ` Jonathan Wakely
2021-06-11 15:43 ` Joseph Myers
2021-06-11 17:02 ` Jonathan Wakely
2021-06-10 11:51 ` [Patch] contrig/gcc-changelog: Check that PR in subject in in changelog (was:: git gcc-commit-mklog doesn't extract PR number to ChangeLog) Tobias Burnus
2021-06-10 11:54 ` [Patch] contrig/gcc-changelog: Check that PR in subject in in changelog Florian Weimer
2021-06-10 12:45 ` Jonathan Wakely
2021-06-10 9:41 ` git gcc-commit-mklog doesn't extract PR number to ChangeLog Jonathan Wakely
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=01eeb5be-809a-182f-fafa-9c3542ea29f8@gmail.com \
--to=msebor@gmail.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=jwakely@redhat.com \
--cc=tobias@codesourcery.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).