Hi all.
Would it be a bad idea to split the Git mailing list up in several
sub-categories?
Example:
announce@
dev@
user@
etc.
The list receives a lot of traffic and it might be beneficial to split
things up.
Anyway, just a suggestion.
Best regards.
Rico
On Sat, Sep 25, 2010 at 21:00, Rico Secada [off-list ref] wrote:
quoted
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
From: walter harms <hidden> Date: 2016-06-15 22:49:37
+1
Rico Secada schrieb:
Hi all.
Would it be a bad idea to split the Git mailing list up in several
sub-categories?
Example:
announce@
dev@
user@
etc.
The list receives a lot of traffic and it might be beneficial to split
things up.
Anyway, just a suggestion.
Best regards.
Rico
--
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
On Sat, Sep 25, 2010 at 23:00, Rico Secada [off-list ref] wrote:
Would it be a bad idea to split the Git mailing list up in several
sub-categories?
Example:
announce@
dev@
user@
Why not, but the simple way is to create another ml for patchs.
Without patchs, the traffic seems relatively low.
--
Sebastien Douche [off-list ref]
Twitter: http://bit.ly/afkrK (agile, lean, python, open source)
On Sun, Sep 26, 2010 at 17:30, Wincent Colaiuta [off-list ref] wrote:
El 26/09/2010, a las 18:02, Sebastien Douche escribió:
quoted
On Sat, Sep 25, 2010 at 23:00, Rico Secada [off-list ref] wrote:
quoted
Would it be a bad idea to split the Git mailing list up in several
sub-categories?
Example:
announce@
dev@
user@
Why not, but the simple way is to create another ml for patchs.
Without patchs, the traffic seems relatively low.
This has come up many times, and been rejected each time. Check the archives for the reasons why.
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.
From: Nicolas Sebrecht <hidden> Date: 2016-06-15 22:49:38
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
From: Adrian Buehlmann <hidden> Date: 2016-06-15 22:49:38
On 25.09.2010 23:00, Rico Secada wrote:
Hi all.
Would it be a bad idea to split the Git mailing list up in several
sub-categories?
Example:
announce@
dev@
user@
etc.
The list receives a lot of traffic and it might be beneficial to split
things up.
I think this would definitely be an improvement for git users. At least
splitting up into dev and user, like Mercurial does it too (which I am
used to). Not sure about announce though.
When I recently subscribed to this list (after having been a long time
subscriber to the Mercurial lists too), I was interested in seeing
discussions about git usage to help me get started with git.
I also think searching the archives would be a bit easier if discussions
of new git development details and its usage would be separated.
On Tue, Sep 28, 2010 at 08:22, Adrian Buehlmann [off-list ref] wrote:
I think this would definitely be an improvement for git users. At least
splitting up into dev and user, like Mercurial does it too (which I am
used to). Not sure about announce though.
So, what is the decision? Split or not split?
--
Sebastien Douche [off-list ref]
Twitter: http://bit.ly/afkrK (agile, lean, python, open source)
From: Leonid Podolny <hidden> Date: 2016-06-15 22:49:40
On Sat, Sep 25, 2010 at 11:00 PM, Rico Secada [off-list ref] wrote:
Hi all.
Would it be a bad idea to split the Git mailing list up in several
sub-categories?
As far as I can tell, splitting a list into -dev and -user lists tends
to drive the quality of the -user list down. The people with actual
knowledge about the topic ask themselves: "Why do I keep answering
questions from clueless noobs, while all the action I care about
happens on another list?" and end up leaving the list altogether.
I think that as long as the traffic on this list remains manageable,
we should keep everything as-is.