From: NightStrike <nightstrike@gmail.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@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: Thu, 19 Jan 2023 14:03:38 -0500 [thread overview]
Message-ID: <CAF1jjLvfq_TLjCOTf2wPp6nRwhyam6St7wvC0O3ZhfAU7EeY8w@mail.gmail.com> (raw)
In-Reply-To: <67368315-70A6-4D5D-9CCE-0890EE0FEB0E@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
On Thu, Jan 19, 2023, 13:33 Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
wrote:
> On 19 January 2023 13:52:55 CET, NightStrike via Fortran <
> fortran@gcc.gnu.org> wrote:
>
> >You can, and people naturally do this, and I think it's great, but
> >there's usually a response from someone saying "post that to the
> >mailing list instead".
>
> The mailing list has a 20-30 year history with reasoning about what
> currently is in the tree. I do think it is valuable to reason about patches
> publically for others to see. And I'm aware that this might not be regarded
> fancy nowadays by everyone.
>
> But that does not mean that using other means to collaborate should not be
> used by some. Be it comp.lang.fortran, a webchat.oftc, or other means,
> that's all fine of course.
>
> patches currently are handled differently, but I don't think that is a
> problem isn't it.
> Just post final patches to the list as long as that is regarded the way to
> do final review and document approval.
>
> cheers,
>
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.
>
next prev parent reply other threads:[~2023-01-19 19:03 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 [this message]
2023-01-20 6:11 ` Bernhard Reutner-Fischer
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=CAF1jjLvfq_TLjCOTf2wPp6nRwhyam6St7wvC0O3ZhfAU7EeY8w@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=benson_muite@emailplus.org \
--cc=fortran@gcc.gnu.org \
--cc=rep.dot.nop@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).