From: Rico Secada <coolzone@it.dk>
To: git@vger.kernel.org
Subject: Re: Splitting the mailing list up
Date: Sat, 25 Sep 2010 23:19:35 +0200 [thread overview]
Message-ID: <20100925231935.8fa0b946.coolzone@it.dk> (raw)
In-Reply-To: <AANLkTikHNhRTTvcpj_30fUBbxv8-qG9HfTTO+XkLJgam@mail.gmail.com>
On Sat, 25 Sep 2010 21:05:12 +0000
Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
> On Sat, Sep 25, 2010 at 21:00, Rico Secada <coolzone@it.dk> wrote:
> > The list receives a lot of traffic and it might be beneficial to
> > split things up.
>
> Why is a lot of traffic a bad thing?
I didn't say it was a bad thing :)
I was looking at this from a "relevancy" point of view. Kinda like the
way Debian or FreeBSD has split their lists up.
> E.g. if you don't want all the patch submissions you can just filter
> out PATCH.
That's one way to do it, but I think splitting things up is better.
Some people live on limited bandwidth and it takes time to download all
emails, especially if you are subscribing to other mailing lists as
well.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-09-25 21:18 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 [this message]
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
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=20100925231935.8fa0b946.coolzone@it.dk \
--to=coolzone@it.dk \
--cc=git@vger.kernel.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 NNTP newsgroup(s).