From: "Jiang, Haochen via Gdb" <gdb@sourceware.org>
To: Joseph Myers <josmyers@redhat.com>,
"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: Tue, 24 Sep 2024 03:43:30 +0000 [thread overview]
Message-ID: <SA1PR11MB5946DB49C30DE25FF0FBB50BEC682@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
In-Reply-To: <b440cf28-674b-122a-160b-0fb96bbf989b@redhat.com>
> From: Joseph Myers <josmyers@redhat.com>
> Sent: Thursday, September 19, 2024 11:51 PM
>
Hi Jospeh,
Thank for your overall introduction on the scope of the future PR
system. It will help the patches not flooded in mails. And keep merging
what we have got in PRs to the right branch to avoid some accidents.
I have several comments or maybe questions on that.
>
> Forge software may provide other pieces such as bug tracking or wikis
> that we currently handle separately from git hosting. In such cases,
> we should be able to disable those pieces and keep using the existing
> bug tracking and wiki software (while having the option to decide
> independently to migrate those if desired).
>
> Similarly, commit emails should continue to go to the existing mailing
> lists for those.
>
Regarding this, it seems that we will still stick to Bugzilla, gcc-wwwdocs,
etc and also keep most of the current mailing threads.
I am running regression tests on x86_64 and sending the regressions to
gcc-regression mailing thread, will I need to send to another place or
using another API to do that?
Note: I am ok to change that if needed, but just in advance so that
I can have some time to test to avoid bugs in scripts.
>
> Beyond putting everything through PRs, eventually I'd hope to have
> merges to mainline normally all go through a CI system that makes sure
> there are no regressions for at least one configuration before merging
> changes.
>
CI might take long time if not just building but running regression tests
from my current experience, it might cause some inconvenience for
someone who only edits something like MAINTAINER lists.
Another question is should we also open a PR for backport commits?
I suppose we need that under current PR infrastructure to get it merged,
but it might be some redundancy. But it is definitely a good thing since
I once backported a patch a month earlier that I expected because I don't
notice I am on the wrong branch.
Also for the current commit for obvious, will that policy change?
Overall, I suppose the PR system will be better than current system, thanks
for all the efforts!
Thx,
Haochen
>
> --
> Joseph S. Myers
> josmyers@redhat.com
next prev parent reply other threads:[~2024-09-24 3:44 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 [this message]
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
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=SA1PR11MB5946DB49C30DE25FF0FBB50BEC682@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