grothoff at in.tum.de
Thu Sep 19 17:55:17 CEST 2013
I dislike the idea of having both on one list, it is likely to simply
decrease the number of subscribers here, without having a meaningful
impact on the number of meaningful code audits. I didn't even know
there was a gnupg-commits mailinglist before, so telling people about
it and asking them to subscribe if they're willing and able to look
over the commits is a better idea.
My 2 cents
On 09/19/2013 05:02 PM, Werner Koch wrote:
> commit logs for git.gnupg.org are send to the gnupg-commits mailing
> list. That is a catch all ML for all GnuPG related commit. However,
> there are only about 70 subscribers and I don't know whether they really
> scan the commits.
> Given that we now see a flow of patch proposals to this list here
> (gcrypt-devel), I wonder whether we may want to send commit logs for
> Libgcrypt also to here. The drawback is that the traffic will increase
> a bit.
> Shall we try that for some time? All branches or just master?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7098 bytes
Desc: not available
More information about the Gcrypt-devel