I checked which mailing lists exist for commons, and it looks like
different repos are configured differently.
e.g. commons-lang has github updates going to issues@, commons-numbers
to notifications@, and a bunch, as we can see, to dev@.
As long as it's consistent, I'm ok with anything, although
On 2019-02-08, Eric Barnhill wrote:
> Is it the consensus outcome for the dev list, that we all receieve a large
> amount of GitBox postings?
I think they are just hitting the wrong mailing list.
We've had notifications of all commits for a long time. In fact this is
a key ingredient for peer re
I agree it would be best to have people watch the repos they're interested in.
If no one objects, I'll open an infra ticket to remove dev@ from
commons-crypto updates. (Will leave it to others to update other
repos.)
On Fri, Feb 8, 2019 at 1:57 PM Eric Barnhill wrote:
>
> Is it the consensus out
Is it the consensus outcome for the dev list, that we all receieve a large
amount of GitBox postings? Wouldn't it be better to leave it to individuals
to track the projects they want to track? I know I do this.
Apologies if I missed any prior discussions.
Eric
