I too agree with others and think that option 1 is better.
On Tue, Oct 6, 2015 at 11:00 PM, Dong Lin wrote:
> I agree with Guozhang.
>
> On Tue, Oct 6, 2015 at 5:49 PM, Gwen Shapira wrote:
>
> > Agree with Guozhang.
> >
> > On Tue, Oct 6, 2015 at 3:22 PM, Guozhang Wang
> wrote:
> >
> > > I thi
I agree with Guozhang.
On Tue, Oct 6, 2015 at 5:49 PM, Gwen Shapira wrote:
> Agree with Guozhang.
>
> On Tue, Oct 6, 2015 at 3:22 PM, Guozhang Wang wrote:
>
> > I think github cannot batch comments in emails (yet?), which is sad..
> >
> > I would prefer to keep both github@kafka / github@kafka-
Agree with Guozhang.
On Tue, Oct 6, 2015 at 3:22 PM, Guozhang Wang wrote:
> I think github cannot batch comments in emails (yet?), which is sad..
>
> I would prefer to keep both github@kafka / github@kafka-site to send only
> open/close PRs unless you subscribe to some tickets.
>
> Guozhang
>
>
I think github cannot batch comments in emails (yet?), which is sad..
I would prefer to keep both github@kafka / github@kafka-site to send only
open/close PRs unless you subscribe to some tickets.
Guozhang
On Tue, Oct 6, 2015 at 9:49 AM, Jiangjie Qin
wrote:
> Hi Ismael,
>
> Thanks for bringing
Hi Ismael,
Thanks for bringing this up. Completely agree the exploding amount of
emails is a little annoying, regardless they are sent to dev list or
personal emails.
Not sure whether it is doable or not, but here is what I am thinking.
1. batch the comments email and send periodically to dev lis
Hi all,
You may have noticed that we receive one email for each comment in
kafka-site pull requests. We don't have that enabled for the kafka (ie
code) repository. Maybe that's OK as the number of emails would be much
higher for the code repository, but I thought it would be good to get other
peop