My only problem with using commits@ is that both GitBox and GitHub will
send the same mails to the same list for the commits.
GitHub also sends emails for discussions in PRs. Those are useful in dev@
but some people complain about them.
On Mon, May 31, 2021, 21:26 Emond Papegaaij
wrote:
> Hi,
Hi,
I agree the mail spams the list a bit and it makes sense to send it
somewhere else, but doesn't it belong in commits@w.a.o?
Best regards,
Emond
On Mon, May 31, 2021 at 5:25 PM Martin Grigorov wrote:
>
> Hi,
>
> Some people complain that there is too much email traffic on dev@ due to
> the
rkurucz9 commented on pull request #471:
URL: https://github.com/apache/wicket/pull/471#issuecomment-851608871
> I've taken a second look and actually your solution is very good. You
clearly have understood how to work with components :).
>
> My major grieve is how the collection of
+1
Why not commits@ ?
from mobile (sorry for typos ;)
On Mon, May 31, 2021, 22:50 Sven Meier wrote:
> +1
>
> Sven
>
> On 31.05.21 17:25, Martin Grigorov wrote:
> > Hi,
> >
> > Some people complain that there is too much email traffic on dev@ due to
> > the GitHub notifications.
> >
> > What
Hi,
Some people complain that there is too much email traffic on dev@ due to
the GitHub notifications.
What do you think about creating a new mailing list, e.g. github@w.a.o ?
This could be easily done via .asf.yaml
Any objections ?
Regards,
Martin
-- Forwarded message -
From:
svenmeier commented on pull request #471:
URL: https://github.com/apache/wicket/pull/471#issuecomment-851249933
I've taken a second look and actually your solution is very good. You
clearly have understood how to work with components :).
My major grieve is how the collection of
