From: NightStrike <nightstrike@gmail.com>
To: Toon Moene <toon@moene.org>
Cc: Benson Muite <benson_muite@emailplus.org>,
gfortran <fortran@gcc.gnu.org>
Subject: Re: Team Collaboration Considerations
Date: Thu, 19 Jan 2023 07:52:55 -0500 [thread overview]
Message-ID: <CAF1jjLsm4tV6NDAyfaPX7jXJx+RJtO4ioLYcgFurxEN1U751Pw@mail.gmail.com> (raw)
In-Reply-To: <532b28b1-4ace-7e8d-21fc-188739f1497f@moene.org>
On Thu, Jan 19, 2023 at 7:46 AM Toon Moene <toon@moene.org> wrote:
>
> On 1/19/23 13:28, NightStrike via Fortran wrote:
>
> > On Thu, Jan 19, 2023, 00:01 Benson Muite via Fortran <fortran@gcc.gnu.org>
> > wrote:
> >
> >> The GCC workflows is quite different from other open source projects
> >> being primarily email based and not using a bug tracker.
> >>
> >
> > There's a bug tracker. I think you mean there isn't a patch tracker (or at
> > least not a system where you submit patches to a thing vs emailing them to
> > a list and hoping someone replies).
> Well, you can put patches into Bugzilla ...
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".
next prev parent reply other threads:[~2023-01-19 12:53 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 [this message]
2023-01-19 18:33 ` Bernhard Reutner-Fischer
2023-01-19 19:03 ` NightStrike
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=CAF1jjLsm4tV6NDAyfaPX7jXJx+RJtO4ioLYcgFurxEN1U751Pw@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=benson_muite@emailplus.org \
--cc=fortran@gcc.gnu.org \
--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).