Hi! As I learned from Twitter the other day, <https://twitter.com/gnutools/status/1439977125243719685>, we now have patchwork set up on sourceware, tracking <gcc-patc...@gcc.gnu.org>: <https://patchwork.sourceware.org/project/gcc/>.
As I'm generally supportive of such "automatism" (if feasible), I wonder: are we going to use that for anything besides eating sourceware resources? ;-) Patchwork may not fit completely well into our current workflow (multiple patches in one email, improper categorization of follow-up emails, etc.), which also relates to what has been discussed at the LPC 2021/GNU Tools track <https://linuxplumbersconf.org/event/11/contributions/995/> "GCC Steering Committee, GLIBC, GDB, Binutils Stewards Q&A". Processes/workflow may change (slowly, I understand...); making progress with these items is separate discussion. But, in particular, I can see how patchwork -- if we agree to actually use it -- may help with one particular case: make sure that patches of new contributors don't get lost "in the noise". Trying to contribute my little share for keeping the "noise" under control, I just tried changing the state of a few patches I know have been pushed, but I'm told: "You don't have permissions to edit [...]". Should not every GCC developer (say, with a <[...]@gcc.gnu.org> email address on file in <https://patchwork.sourceware.org/user/>) be able to do any such changes (like in Bugzilla)? Also, we'll need some user guide: web page, or wiki page, or, preferably?, on <https://patchwork.sourceware.org/project/gcc/> itself. How are we using the different states, archived, bundles, etc. I bet Carlos and team have all this sorted out for glibc already, so we may "just" copy that for GCC? ;-P Grüße Thomas ----------------- Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
