From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Wincent Colaiuta <win@wincent.com>,
Sebastien Douche <sdouche@gmail.com>,
Rico Secada <coolzone@it.dk>,
git@vger.kernel.org, Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: Splitting the mailing list up
Date: Mon, 27 Sep 2010 18:53:56 +0200 [thread overview]
Message-ID: <20100927165356.GA13032@vidovic> (raw)
In-Reply-To: <AANLkTik3ES08H1VSaGxv7aDoV3Ki_Y2ea2dHYqem0S28@mail.gmail.com>
The 26/09/10, Ævar Arnfjörð Bjarmason wrote:
> Right, but for the *main* mailing list. However if Rico, Walter and
> others would find a limited traffic mailing list valuable there's
> nothing stopping them from setting one up.
>
> Jay linked to an archive where someone is running RSS feeds of the
> different parts of the git list, similarly you could set up a git-user
> list which would be a version of the git list filtered to reduce patch
> traffic.
>
> Maybe that list wouldn't make much sense when patches are intermingled
> with regular discussion, but it's worth a try.
zsh mailing lists(1) are splitted in users and workers where submissions
in the users list are forwarded to workers. This looks like a good
solution for the git mailing list(s), IMHO.
1. http://zsh.sourceforge.net/Arc/mlist.html
--
Nicolas Sebrecht
next prev parent reply other threads:[~2010-09-27 16:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 21:00 Splitting the mailing list up Rico Secada
2010-09-25 21:05 ` Ævar Arnfjörð Bjarmason
2010-09-25 21:19 ` Rico Secada
2010-09-26 6:52 ` Jay Soffian
2010-09-26 15:58 ` walter harms
2010-09-26 16:02 ` Sebastien Douche
2010-09-26 17:30 ` Wincent Colaiuta
2010-09-26 18:54 ` Ævar Arnfjörð Bjarmason
2010-09-27 16:53 ` Nicolas Sebrecht [this message]
2010-09-28 6:22 ` Adrian Buehlmann
2010-09-29 7:56 ` Sebastien Douche
[not found] ` <141CAFB5-D423-48FE-BEED-B755C5F2685B@sb.org>
2010-09-29 8:36 ` Adrian Buehlmann
2010-09-29 9:08 ` Michael J Gruber
2010-09-29 13:00 ` Erik Faye-Lund
2010-09-29 13:20 ` Adrian Buehlmann
2010-09-29 13:30 ` Erik Faye-Lund
2010-09-29 15:02 ` Sverre Rabbelier
2010-10-02 21:33 ` Brandon Casey
2010-10-02 18:26 ` Leonid Podolny
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=20100927165356.GA13032@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=avarab@gmail.com \
--cc=coolzone@it.dk \
--cc=git@vger.kernel.org \
--cc=sdouche@gmail.com \
--cc=win@wincent.com \
/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 NNTP newsgroup(s).