[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Separate Mailing Lists for Patches vs General Dev Discussion?
From: |
Danny Milosavljevic |
Subject: |
Re: Separate Mailing Lists for Patches vs General Dev Discussion? |
Date: |
Tue, 26 Jul 2016 18:25:16 +0200 |
Hi,
On Mon, 25 Jul 2016 22:35:57 +0200
Florian Paul Schmidt <address@hidden> wrote:
> 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?
I think it would be easier if you created a filter rule in your mail user agent
that filters out E-Mails that have subjects that start with "[PATCH". No need
to seperate mailinglists at the server for that. Also, maybe you will want to
look at a patch later, and then you have to subscribe to the other list. There
are enough barriers to contribution already. Patches are posted here in order
to invite discussion, it's not a commit autobot that posts them or anything.
Also, at least I post patches as response to non-patch discussions as well -
that's important for context. I even post bug reports as response to other
posts - also for context. This context would be lost in your scenario.
I don't see why one would subscribe to the devel mailing list if one didn't
want to see patches. I mean what would the development consist of? Writing
poems? :)
There's a user help list, help-guix. I'm not subscribed to it. Just now I
checked help-guix archives and there was a discussion about Guix on ARM I would
have been interested in but completely missed. Creating another list would make
it worse in my opinion.
Re: Separate Mailing Lists for Patches vs General Dev Discussion?,
Danny Milosavljevic <=