Re: Move GitBox notifications to commits list?
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 SUwrote: > Agree. How to set it to move gitbox notifications to notifications@? > > 2018-04-16 18:03 GMT+08:00 John D. Ament : > > > 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 > > wrote: > > > > > On Sun, Apr 8, 2018 at 9:55 AM Daniel Gruno > > 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-unsubscr...@echarts.apache.org > > >> For additional commands, e-mail: dev-h...@echarts.apache.org > > >> > > >> > > >
Re: Move GitBox notifications to commits list?
Agree. How to set it to move gitbox notifications to notifications@? 2018-04-16 18:03 GMT+08:00 John D. Ament: > 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 > wrote: > > > On Sun, Apr 8, 2018 at 9:55 AM Daniel Gruno > 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-unsubscr...@echarts.apache.org > >> For additional commands, e-mail: dev-h...@echarts.apache.org > >> > >> >
Re: Move GitBox notifications to commits list?
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. Amentwrote: > On Sun, Apr 8, 2018 at 9:55 AM Daniel Gruno 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-unsubscr...@echarts.apache.org >> For additional commands, e-mail: dev-h...@echarts.apache.org >> >>
Re: Move GitBox notifications to commits list?
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-unsubscr...@echarts.apache.org For additional commands, e-mail: dev-h...@echarts.apache.org