From: "Jiang, Haochen via Gdb" <gdb@sourceware.org>
To: Joseph Myers <josmyers@redhat.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"binutils@sourceware.org" <binutils@sourceware.org>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: On pull request workflows for the GNU toolchain
Date: Thu, 26 Sep 2024 01:42:30 +0000 [thread overview]
Message-ID: <SA1PR11MB594641CAD01185825F18A47FEC6A2@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
In-Reply-To: <5895fc8d-c1ea-d082-4696-da52b275fe9e@redhat.com>
> From: Joseph Myers <josmyers@redhat.com>
> Sent: Wednesday, September 25, 2024 10:46 PM
>
> On Wed, 25 Sep 2024, Jiang, Haochen via Gcc wrote:
>
> > The potential issue might be the PR will be closed after merging, which might
> > be flooded in history if the regression is not fixed with the PR forgotten to be
> > reopened. I am not sure the reopen could be automatically done. If it could,
>
> I think reopening is for when a PR was reverted after being merged; not
> for when a regression was found but is going to be addressed through
> subsequent fix commits rather than through reverting. You might want to
> file a bug in Bugzilla for the regression (automatically or otherwise),
> however.
I will have a try on that when I have some time. Maybe in GCC stage 3 I
suppose since I plan to go through the current regressions to see if it is
fixed and the regression framework to see if it can improve at that time.
Thx,
Haochen
>
> --
> Joseph S. Myers
> josmyers@redhat.com
prev parent reply other threads:[~2024-09-26 1:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 15:51 Joseph Myers via Gdb
2024-09-20 18:25 ` Carlos O'Donell via Gdb
2024-09-20 20:41 ` Joseph Myers via Gdb
2024-09-20 21:43 ` Sam James via Gdb
2024-09-20 19:58 ` Matt Rice via Gdb
2024-09-20 20:47 ` Joseph Myers via Gdb
2024-09-23 12:07 ` Thomas Koenig via Gdb
2024-09-23 12:53 ` Jeffrey Walton via Gdb
2024-09-23 13:23 ` Jonathan Wakely via Gdb
2024-09-23 13:36 ` enh via Gdb
2024-09-23 14:33 ` Jonathan Wakely via Gdb
2024-09-23 15:56 ` Iain Sandoe
2024-09-23 15:03 ` Joseph Myers via Gdb
2024-09-23 15:20 ` Florian Weimer via Gdb
2024-09-23 15:44 ` Jonathan Wakely via Gdb
2024-09-23 17:57 ` Eric Gallager via Gdb
2024-09-23 18:39 ` Jonathan Wakely via Gdb
2024-09-23 18:30 ` Arsen Arsenović via Gdb
2024-09-23 12:56 ` Richard Earnshaw (lists) via Gdb
2024-09-23 14:59 ` Joseph Myers via Gdb
2024-09-24 3:43 ` Jiang, Haochen via Gdb
2024-09-24 16:42 ` Joseph Myers via Gdb
2024-09-25 3:01 ` Jiang, Haochen via Gdb
2024-09-25 14:46 ` Joseph Myers via Gdb
2024-09-26 1:42 ` Jiang, Haochen via Gdb [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=SA1PR11MB594641CAD01185825F18A47FEC6A2@SA1PR11MB5946.namprd11.prod.outlook.com \
--to=gdb@sourceware.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=haochen.jiang@intel.com \
--cc=josmyers@redhat.com \
--cc=libc-alpha@sourceware.org \
/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