You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@echarts.apache.org by "John D. Ament" <jo...@apache.org> on 2018/04/08 13:53:30 UTC

Move GitBox notifications to commits list?

Hi,

I find it a bit difficult to sift through the developer activities.  Right
now, all gitbox notifications are going to dev@.  I think they make more
sense to go to commits@, potentially an issues@ list.

What do others think?

John

Re: Move GitBox notifications to commits list?

Posted by Wenli Zhang <ov...@gmail.com>.
Agree. Could one of our mentor help to configure? Or tell us how to do so?
Thanks!

Zhang Wenli
http://zhangwenli.com

On Tue, Apr 17, 2018 at 4:27 AM, SHUANG SU <su...@gmail.com> wrote:

> Agree. How to set it to move gitbox notifications to notifications@?
>
> 2018-04-16 18:03 GMT+08:00 John D. Ament <jo...@apache.org>:
>
> > Hi all
> >
> > Just a friendly ping from a mentor.  I like to stay up on the dev
> > discussions, but tons of gitbox mails flowing in.
> >
> > Another podling of mine went with a notifications@ list.
> >
> > John
> >
> > On Sun, Apr 8, 2018 at 10:17 AM John D. Ament <jo...@apache.org>
> > wrote:
> >
> > > On Sun, Apr 8, 2018 at 9:55 AM Daniel Gruno <hu...@apache.org>
> > wrote:
> > >
> > >> On 04/08/2018 03:53 PM, John D. Ament wrote:
> > >> > Hi,
> > >> >
> > >> > I find it a bit difficult to sift through the developer activities.
> > >> Right
> > >> > now, all gitbox notifications are going to dev@.  I think they make
> > >> more
> > >> > sense to go to commits@, potentially an issues@ list.
> > >> >
> > >> > What do others think?
> > >> >
> > >> > John
> > >> >
> > >>
> > >> or make an issues@ list? Would be nice if we had it split three ways:
> > >>
> > >> dev@: development discussions
> > >> issues@: PRs etc
> > >> commits: git commits
> > >>
> > >>
> > > How would you classify the comments added to a PR?  issues@? or
> commits@
> > ?
> > >
> > >
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@echarts.apache.org
> > >> For additional commands, e-mail: dev-help@echarts.apache.org
> > >>
> > >>
> >
>

Re: Move GitBox notifications to commits list?

Posted by SHUANG SU <su...@gmail.com>.
Agree. How to set it to move gitbox notifications to notifications@?

2018-04-16 18:03 GMT+08:00 John D. Ament <jo...@apache.org>:

> Hi all
>
> Just a friendly ping from a mentor.  I like to stay up on the dev
> discussions, but tons of gitbox mails flowing in.
>
> Another podling of mine went with a notifications@ list.
>
> John
>
> On Sun, Apr 8, 2018 at 10:17 AM John D. Ament <jo...@apache.org>
> wrote:
>
> > On Sun, Apr 8, 2018 at 9:55 AM Daniel Gruno <hu...@apache.org>
> wrote:
> >
> >> On 04/08/2018 03:53 PM, John D. Ament wrote:
> >> > Hi,
> >> >
> >> > I find it a bit difficult to sift through the developer activities.
> >> Right
> >> > now, all gitbox notifications are going to dev@.  I think they make
> >> more
> >> > sense to go to commits@, potentially an issues@ list.
> >> >
> >> > What do others think?
> >> >
> >> > John
> >> >
> >>
> >> or make an issues@ list? Would be nice if we had it split three ways:
> >>
> >> dev@: development discussions
> >> issues@: PRs etc
> >> commits: git commits
> >>
> >>
> > How would you classify the comments added to a PR?  issues@? or commits@
> ?
> >
> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@echarts.apache.org
> >> For additional commands, e-mail: dev-help@echarts.apache.org
> >>
> >>
>

Re: Move GitBox notifications to commits list?

Posted by "John D. Ament" <jo...@apache.org>.
Hi all

Just a friendly ping from a mentor.  I like to stay up on the dev
discussions, but tons of gitbox mails flowing in.

Another podling of mine went with a notifications@ list.

John

On Sun, Apr 8, 2018 at 10:17 AM John D. Ament <jo...@apache.org> wrote:

> On Sun, Apr 8, 2018 at 9:55 AM Daniel Gruno <hu...@apache.org> wrote:
>
>> On 04/08/2018 03:53 PM, John D. Ament wrote:
>> > Hi,
>> >
>> > I find it a bit difficult to sift through the developer activities.
>> Right
>> > now, all gitbox notifications are going to dev@.  I think they make
>> more
>> > sense to go to commits@, potentially an issues@ list.
>> >
>> > What do others think?
>> >
>> > John
>> >
>>
>> or make an issues@ list? Would be nice if we had it split three ways:
>>
>> dev@: development discussions
>> issues@: PRs etc
>> commits: git commits
>>
>>
> How would you classify the comments added to a PR?  issues@? or commits@?
>
>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@echarts.apache.org
>> For additional commands, e-mail: dev-help@echarts.apache.org
>>
>>

Re: Move GitBox notifications to commits list?

Posted by "John D. Ament" <jo...@apache.org>.
On Sun, Apr 8, 2018 at 9:55 AM Daniel Gruno <hu...@apache.org> wrote:

> On 04/08/2018 03:53 PM, John D. Ament wrote:
> > Hi,
> >
> > I find it a bit difficult to sift through the developer activities.
> Right
> > now, all gitbox notifications are going to dev@.  I think they make more
> > sense to go to commits@, potentially an issues@ list.
> >
> > What do others think?
> >
> > John
> >
>
> or make an issues@ list? Would be nice if we had it split three ways:
>
> dev@: development discussions
> issues@: PRs etc
> commits: git commits
>
>
How would you classify the comments added to a PR?  issues@? or commits@?


>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@echarts.apache.org
> For additional commands, e-mail: dev-help@echarts.apache.org
>
>

Re: Move GitBox notifications to commits list?

Posted by Daniel Gruno <hu...@apache.org>.
On 04/08/2018 03:53 PM, John D. Ament wrote:
> Hi,
> 
> I find it a bit difficult to sift through the developer activities.  Right
> now, all gitbox notifications are going to dev@.  I think they make more
> sense to go to commits@, potentially an issues@ list.
> 
> What do others think?
> 
> John
> 

or make an issues@ list? Would be nice if we had it split three ways:

dev@: development discussions
issues@: PRs etc
commits: git commits


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@echarts.apache.org
For additional commands, e-mail: dev-help@echarts.apache.org