Craig, Ben via llvm-dev
2016-Jul-05 19:04 UTC
[llvm-dev] Suggestion to Stop Cross Posting Discussions
+1 to do something, whether that something is to mail only on llvm-dev, or to move those discussions to a 'community' or 'cross-project' list of some sort. I -am- subscribed to cfe-def and llvm-dev, and as a result, I get most of these messages twice. I also have mail rules to put cfe-dev email in one folder and llvm-dev email in another folder. When both mailing lists are involved, the discussions end up in my llvm-dev folder, but occasionally, someone will only reply on one of the lists. I then get to follow the discussion across folders, and that's no fun. On 7/5/2016 1:59 PM, Hal Finkel via llvm-dev wrote:> ----- Original Message ----- >> From: "John Criswell via llvm-dev" <llvm-dev at lists.llvm.org> >> To: llvm-dev at lists.llvm.org >> Sent: Tuesday, July 5, 2016 1:51:27 PM >> Subject: [llvm-dev] Suggestion to Stop Cross Posting Discussions >> >> Dear All, >> >> Within the past few months, there have been several discussions that >> relate to LLVM and its sub-projects (such as the discussions on >> moving >> to Git and the Code of Conduct). To ensure that these discussions >> reach >> all community members, people have been cross-posting these messages >> to >> llvmdev, cfe-dev, and every other -dev you can think of. >> >> This is becoming a headache for me (and possibly other mailing list >> admins) because replies are often sent to every list, but not all >> users >> are subscribed to every list. As a result, we're moderating messages >> for people because they're subscribed to llvm-dev but not openmp-dev, >> or >> they are on cfe-dev but not llvm-dev, etc. >> >> Can we keep these policy discussions on llvm-dev and just expect >> people >> to subscribe to llvm-dev if they want to particpate? Alternatively, >> could we create a new mailing list for these discussions? >> >> I'd rather spend time moderating first-poster posts and discarding >> SPAM >> than ensuring that all of you can post to all the lists. > Perhaps this is the easiest solution: Make it so that anyone subscribed to any of the -dev lists can post to all of them. > > Alternatively, we could have a "community" list to which anyone subscribed to any of the -dev lists is automatically subscribed. > > We have a lot of people who are subscribed, for example, to cfe-dev and not to llvm-dev, and I'm not sure that making them received backend-related messages just to catch community-wide discussions is reasonable. > > -Hal > >> Regards, >> >> John Criswell >> >> -- >> John Criswell >> Assistant Professor >> Department of Computer Science, University of Rochester >> http://www.cs.rochester.edu/u/criswell >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >>-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
Daniel Sanders via llvm-dev
2016-Jul-06 09:11 UTC
[llvm-dev] Suggestion to Stop Cross Posting Discussions
+1. I have a similar setup but I only seem to end up with one copy for some reason. It's very confusing to read the end of the conversation on llvm-dev, the beginning on cfe-dev, and finally the middle on lldb-dev.> -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Craig, > Ben via llvm-dev > Sent: 05 July 2016 20:05 > To: llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] Suggestion to Stop Cross Posting Discussions > > +1 to do something, whether that something is to mail only on llvm-dev, > or to move those discussions to a 'community' or 'cross-project' list of > some sort. > > I -am- subscribed to cfe-def and llvm-dev, and as a result, I get most > of these messages twice. I also have mail rules to put cfe-dev email in > one folder and llvm-dev email in another folder. When both mailing lists > are involved, the discussions end up in my llvm-dev folder, but > occasionally, someone will only reply on one of the lists. I then get > to follow the discussion across folders, and that's no fun. > > > On 7/5/2016 1:59 PM, Hal Finkel via llvm-dev wrote: > > ----- Original Message ----- > >> From: "John Criswell via llvm-dev" <llvm-dev at lists.llvm.org> > >> To: llvm-dev at lists.llvm.org > >> Sent: Tuesday, July 5, 2016 1:51:27 PM > >> Subject: [llvm-dev] Suggestion to Stop Cross Posting Discussions > >> > >> Dear All, > >> > >> Within the past few months, there have been several discussions that > >> relate to LLVM and its sub-projects (such as the discussions on > >> moving > >> to Git and the Code of Conduct). To ensure that these discussions > >> reach > >> all community members, people have been cross-posting these messages > >> to > >> llvmdev, cfe-dev, and every other -dev you can think of. > >> > >> This is becoming a headache for me (and possibly other mailing list > >> admins) because replies are often sent to every list, but not all > >> users > >> are subscribed to every list. As a result, we're moderating messages > >> for people because they're subscribed to llvm-dev but not openmp-dev, > >> or > >> they are on cfe-dev but not llvm-dev, etc. > >> > >> Can we keep these policy discussions on llvm-dev and just expect > >> people > >> to subscribe to llvm-dev if they want to particpate? Alternatively, > >> could we create a new mailing list for these discussions? > >> > >> I'd rather spend time moderating first-poster posts and discarding > >> SPAM > >> than ensuring that all of you can post to all the lists. > > Perhaps this is the easiest solution: Make it so that anyone subscribed to > any of the -dev lists can post to all of them. > > > > Alternatively, we could have a "community" list to which anyone > subscribed to any of the -dev lists is automatically subscribed. > > > > We have a lot of people who are subscribed, for example, to cfe-dev and > not to llvm-dev, and I'm not sure that making them received backend-related > messages just to catch community-wide discussions is reasonable. > > > > -Hal > > > >> Regards, > >> > >> John Criswell > >> > >> -- > >> John Criswell > >> Assistant Professor > >> Department of Computer Science, University of Rochester > >> http://www.cs.rochester.edu/u/criswell > >> > >> _______________________________________________ > >> LLVM Developers mailing list > >> llvm-dev at lists.llvm.org > >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > >> > > -- > Employee of Qualcomm Innovation Center, Inc. > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a > Linux Foundation Collaborative Project > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
Robinson, Paul via llvm-dev
2016-Jul-06 15:03 UTC
[llvm-dev] Suggestion to Stop Cross Posting Discussions
> -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of > Daniel Sanders via llvm-dev > Sent: Wednesday, July 06, 2016 2:11 AM > To: Craig, Ben; llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] Suggestion to Stop Cross Posting Discussions > > +1. I have a similar setup but I only seem to end up with one copy for > some reason. It's very confusing to read the end of the conversation on > llvm-dev, the beginning on cfe-dev, and finally the middle on lldb-dev.I move *-dev to a single folder just to avoid this. The sum of all *-dev traffic is not that much. --paulr> > > -----Original Message----- > > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of > Craig, > > Ben via llvm-dev > > Sent: 05 July 2016 20:05 > > To: llvm-dev at lists.llvm.org > > Subject: Re: [llvm-dev] Suggestion to Stop Cross Posting Discussions > > > > +1 to do something, whether that something is to mail only on llvm-dev, > > or to move those discussions to a 'community' or 'cross-project' list of > > some sort. > > > > I -am- subscribed to cfe-def and llvm-dev, and as a result, I get most > > of these messages twice. I also have mail rules to put cfe-dev email in > > one folder and llvm-dev email in another folder. When both mailing lists > > are involved, the discussions end up in my llvm-dev folder, but > > occasionally, someone will only reply on one of the lists. I then get > > to follow the discussion across folders, and that's no fun. > > > > > > On 7/5/2016 1:59 PM, Hal Finkel via llvm-dev wrote: > > > ----- Original Message ----- > > >> From: "John Criswell via llvm-dev" <llvm-dev at lists.llvm.org> > > >> To: llvm-dev at lists.llvm.org > > >> Sent: Tuesday, July 5, 2016 1:51:27 PM > > >> Subject: [llvm-dev] Suggestion to Stop Cross Posting Discussions > > >> > > >> Dear All, > > >> > > >> Within the past few months, there have been several discussions that > > >> relate to LLVM and its sub-projects (such as the discussions on > > >> moving > > >> to Git and the Code of Conduct). To ensure that these discussions > > >> reach > > >> all community members, people have been cross-posting these messages > > >> to > > >> llvmdev, cfe-dev, and every other -dev you can think of. > > >> > > >> This is becoming a headache for me (and possibly other mailing list > > >> admins) because replies are often sent to every list, but not all > > >> users > > >> are subscribed to every list. As a result, we're moderating messages > > >> for people because they're subscribed to llvm-dev but not openmp-dev, > > >> or > > >> they are on cfe-dev but not llvm-dev, etc. > > >> > > >> Can we keep these policy discussions on llvm-dev and just expect > > >> people > > >> to subscribe to llvm-dev if they want to particpate? Alternatively, > > >> could we create a new mailing list for these discussions? > > >> > > >> I'd rather spend time moderating first-poster posts and discarding > > >> SPAM > > >> than ensuring that all of you can post to all the lists. > > > Perhaps this is the easiest solution: Make it so that anyone > subscribed to > > any of the -dev lists can post to all of them. > > > > > > Alternatively, we could have a "community" list to which anyone > > subscribed to any of the -dev lists is automatically subscribed. > > > > > > We have a lot of people who are subscribed, for example, to cfe-dev > and > > not to llvm-dev, and I'm not sure that making them received backend- > related > > messages just to catch community-wide discussions is reasonable. > > > > > > -Hal > > > > > >> Regards, > > >> > > >> John Criswell > > >> > > >> -- > > >> John Criswell > > >> Assistant Professor > > >> Department of Computer Science, University of Rochester > > >> http://www.cs.rochester.edu/u/criswell > > >> > > >> _______________________________________________ > > >> LLVM Developers mailing list > > >> llvm-dev at lists.llvm.org > > >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > >> > > > > -- > > Employee of Qualcomm Innovation Center, Inc. > > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a > > Linux Foundation Collaborative Project > > > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llvm.org > > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev