> > ... resolutions are more important to you than creations. > Thanks for offering to help with filters, Alan, I might take you up on that someday. But I try not to wait for commits before checking doc issues. It seems rude to ask for parameter description changes after a commit.
The filter I really want would check all *patches* for HiveConf.java parameters. That's not possible, is it? All commits are already sent to the commits list ... Um ... what is the commits list? (Assuming you don't mean the release list.) A general question: Would the non-creation JIRA list actually exclude creation messages, or would those go to both lists? Not sure if that matters, just curious. -- Lefty On Fri, Nov 21, 2014 at 5:44 PM, Gunther Hagleitner < ghagleit...@hortonworks.com> wrote: > +1 > > Thanks, > Gunther. > > On Fri, Nov 21, 2014 at 5:41 PM, Thejas Nair <the...@hortonworks.com> > wrote: > > > +1 > > > > On Fri, Nov 21, 2014 at 5:16 PM, Alan Gates <ga...@hortonworks.com> > wrote: > > > > > Do you mean RB creation? I wouldn't be in favor of sending all RB > > > activity to it, since we're trying to create a low traffic list. > > > > > > Alan. > > > > > > Brock Noland <br...@cloudera.com> > > > November 21, 2014 at 17:10 > > > I think that RB activity could be put on this same list? > > > > > > > > > Brock Noland <br...@cloudera.com> > > > November 21, 2014 at 17:09 > > > +1 > > > > > > > > > Szehon Ho <sze...@cloudera.com> > > > November 21, 2014 at 17:03 > > > +1. Create + resolve might be a good idea too, as I imagine > contributors > > > might want to see what is changing in Hive, and not just issues > created. > > > > > > Thanks, > > > Szehon > > > > > > On Fri, Nov 21, 2014 at 1:15 PM, Prasanth Jayachandran < > > > > > > Prasanth Jayachandran <pjayachand...@hortonworks.com> > > > November 21, 2014 at 13:15 > > > +1 > > > > > > > > > - Prasanth > > > > > > Alan Gates <ga...@hortonworks.com> > > > November 21, 2014 at 12:59 > > > Poke, I got some scattered +1s but I'd like to get feedback from a > > higher > > > percentage of committers before filing the infra ticket to do this. Or > > > maybe a better way to put it is, is anyone opposed? > > > > > > Lefty, to answer your question, we could include resolutions as well. > > But > > > that doubles the traffic going to the dev list. I get why you're > > concerned > > > with it, since resolutions are more important to you than creations. > I'm > > > happy to help you set up a filter on the list with the non-creation > JIRA > > > traffic so you can just see the resolutions. > > > > > > Alan. > > > > > > > > > > > > -- > > > Sent with Postbox <http://www.getpostbox.com> > > > > > > CONFIDENTIALITY NOTICE > > > NOTICE: This message is intended for the use of the individual or > entity > > > to which it is addressed and may contain information that is > > confidential, > > > privileged and exempt from disclosure under applicable law. If the > reader > > > of this message is not the intended recipient, you are hereby notified > > that > > > any printing, copying, dissemination, distribution, disclosure or > > > forwarding of this communication is strictly prohibited. If you have > > > received this communication in error, please contact the sender > > immediately > > > and delete it from your system. Thank You. > > > > > > > -- > > CONFIDENTIALITY NOTICE > > NOTICE: This message is intended for the use of the individual or entity > to > > which it is addressed and may contain information that is confidential, > > privileged and exempt from disclosure under applicable law. If the reader > > of this message is not the intended recipient, you are hereby notified > that > > any printing, copying, dissemination, distribution, disclosure or > > forwarding of this communication is strictly prohibited. If you have > > received this communication in error, please contact the sender > immediately > > and delete it from your system. Thank You. > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >