From: Vincent Legoll <vincent.legoll@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Separate Mailing Lists for Patches vs General Dev Discussion?
Date: Tue, 26 Jul 2016 14:47:28 +0200 [thread overview]
Message-ID: <CAEwRq=qotATW6Pup60C05BUoqZZ0G4h5piX+MdHWSaUG=GJ5CQ@mail.gmail.com> (raw)
In-Reply-To: <8760rsa88t.fsf@gnu.org>
I'm not sure a separate additional ML would enhance the situation,
the combined volume is low enough to let them stay together.
But resurrection & real use of patchwork (or any other consensus
web tracker) would be a plus for at least some of us newcomers
from different horizons.
I can understand the repulsion against some of them, but a PR-like
enabled one could ease the on-boarding of new contributors. So if
it's acceptable to committers, why not try to use one a bit more
regularly ?
--
Vincent Legoll
next prev parent reply other threads:[~2016-07-26 12:47 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
2016-07-26 12:47 ` Vincent Legoll [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEwRq=qotATW6Pup60C05BUoqZZ0G4h5piX+MdHWSaUG=GJ5CQ@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).