From: ludo@gnu.org (Ludovic Courtès)
To: Florian Paul Schmidt <mista.tapas@gmx.net>
Cc: guix-devel@gnu.org
Subject: Re: Separate Mailing Lists for Patches vs General Dev Discussion?
Date: Tue, 26 Jul 2016 14:34:10 +0200 [thread overview]
Message-ID: <8760rsa88t.fsf@gnu.org> (raw)
In-Reply-To: <5796782D.1010104@gmx.net> (Florian Paul Schmidt's message of "Mon, 25 Jul 2016 22:35:57 +0200")
Hello!
Florian Paul Schmidt <mista.tapas@gmx.net> skribis:
> I'm following the Guix-Project, even if not contributing much because
> of time constraints. The one, very simple to implement, thing that
> would make following the project more easy IMHO would be a separate
> list for patches. Or maybe the other way around: A separate list for
> more general discussion :)
>
> What do you think?
GCC has a gcc-patches@ mailing list in addition to gcc@. However, as a
passerby, I found it’s not super clear whether to use gcc@, or
gcc-patches@, or the Bugzilla instance. So I’m not sure it would
improve the situation.
Thoughts?
FWIW, I filter help-guix, guix-devel, and guix-sysadmin in separate
folders, and then I use Gnus’ scoring mechanism for things in guix-devel
(you could assign a low score to messages whose subject contains
“[PATCH]” for instance.)
Ludo’.
next prev parent reply other threads:[~2016-07-26 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 20:35 Separate Mailing Lists for Patches vs General Dev Discussion? Florian Paul Schmidt
2016-07-26 10:44 ` ng0
2016-07-26 11:23 ` Andreas Enge
2016-07-26 12:34 ` Ludovic Courtès [this message]
2016-07-26 12:47 ` Vincent Legoll
2016-07-27 22:05 ` Ludovic Courtès
2016-07-29 11:56 ` Vincent Legoll
2016-07-29 15:28 ` Leo Famulari
2016-07-26 16:25 ` Danny Milosavljevic
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=8760rsa88t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mista.tapas@gmx.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.