From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: NightStrike via Fortran <fortran@gcc.gnu.org>,
Toon Moene <toon@moene.org>,
Benson Muite <benson_muite@emailplus.org>
Subject: Re: Team Collaboration Considerations
Date: Fri, 20 Jan 2023 07:11:27 +0100 [thread overview]
Message-ID: <0C304C65-7490-4794-B6B9-2B4C2FE9A542@gmail.com> (raw)
In-Reply-To: <CAF1jjLvfq_TLjCOTf2wPp6nRwhyam6St7wvC0O3ZhfAU7EeY8w@mail.gmail.com>
On 19 January 2023 20:03:38 CET, NightStrike <nightstrike@gmail.com> wrote:
>The problem is that patch tracking is unsustainable. You could go the other
>way and have a patch tracker automatically echo messages to the mailing
>list.
Currently it's the other way round. Patchwork collects the patches sent to the list. Everybody is free to administrate her patches in Patchwork iff that is desired.
Or do the same but through bugzilla.
I am aware that all this might not be the way you envision things to work, of course.
next prev parent reply other threads:[~2023-01-20 6:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 3:52 Jerry D
2022-12-04 14:16 ` Benson Muite
2022-12-08 1:54 ` Jerry D
2022-12-08 4:12 ` Benson Muite
2022-12-08 16:27 ` Steve Kargl
2022-12-08 17:25 ` Tobias Burnus
2022-12-10 18:15 ` Jerry D
2022-12-08 19:14 ` Holcomb, Katherine A (kah3f)
2022-12-09 19:36 ` Toon Moene
2022-12-09 21:56 ` Paul Richard Thomas
2022-12-09 22:10 ` Toon Moene
2022-12-10 20:10 ` Jerry D
2022-12-10 21:09 ` Steve Kargl
2022-12-11 17:37 ` Holcomb, Katherine A (kah3f)
2022-12-10 21:11 ` Thomas Koenig
2022-12-13 8:10 ` Janne Blomqvist
2022-12-13 12:22 ` Jerry D
2022-12-26 10:19 ` NightStrike
2023-01-19 5:00 ` Benson Muite
2023-01-19 12:28 ` NightStrike
2023-01-19 12:46 ` Toon Moene
2023-01-19 12:52 ` NightStrike
2023-01-19 18:33 ` Bernhard Reutner-Fischer
2023-01-19 19:03 ` NightStrike
2023-01-20 6:11 ` Bernhard Reutner-Fischer [this message]
2023-01-20 6:21 ` Benson Muite
2023-01-21 4:50 ` Jerry D
2022-12-08 21:27 Harald Anlauf
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=0C304C65-7490-4794-B6B9-2B4C2FE9A542@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=benson_muite@emailplus.org \
--cc=fortran@gcc.gnu.org \
--cc=nightstrike@gmail.com \
--cc=toon@moene.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).