Ok, thank you. Let's see how it goes. I still think the emails from the git2jira comments (or the comments themselves) tend not to be very informative. :-)
I appreciate your taking action quickly! Remko Sent from my iPhone > On Jan 19, 2017, at 1:20, Matt Sicker <boa...@gmail.com> wrote: > > I just requested that they only enable the git2jira integration for master. I > also requested if we can get rid of merge commit emails on topic branches or > if we can just disable non-master commits from spamming the list. I find that > it's nearly impossible to review a topic branch via those commit messages > anyways, so I'd normally pull it locally and do a diff or check it out in > GitHub. > >> On 18 January 2017 at 10:15, Matt Sicker <boa...@gmail.com> wrote: >> The merging master to topic branches causing commit messages on the list is >> the real problem here I think. I'll make a couple infra requests to try and >> reduce some spamminess. >> >>> On 18 January 2017 at 05:40, Remko Popma <remko.po...@gmail.com> wrote: >>> +1 >>> >>> It seemed like a good idea but I have trouble keeping up. Too many emails... >>> >>> I already have trouble keeping up with the commit emails and the list >>> traffic, and these JIRA entries add more traffic that don't really tell me >>> anything new. What do you think? >>> >>> >>> Sent from my iPhone >>> >>>> On Jan 18, 2017, at 17:56, Mikael Ståldal <mikael.stal...@magine.com> >>>> wrote: >>>> >>>> It seems to be a bit spammy though. When I merged master into my branch, >>>> all those commits trigger notification again. Can we maybe restrict it to >>>> only monitor master branch? >>>> >>>>> On Mon, Jan 16, 2017 at 12:29 AM, Matt Sicker <boa...@gmail.com> wrote: >>>>> It appears this feature is enabled and working. >>>>> >>>>>> On 15 January 2017 at 12:58, Matt Sicker <boa...@gmail.com> wrote: >>>>>> I made an infra request to enable this. Not sure how long it'll take to >>>>>> get enabled. >>>>>> >>>>>>> On 15 January 2017 at 12:56, Mikael Ståldal <mikael.stal...@magine.com> >>>>>>> wrote: >>>>>>> Sounds good. >>>>>>> >>>>>>>> On Jan 15, 2017 5:33 AM, "Remko Popma" <remko.po...@gmail.com> wrote: >>>>>>>> Sounds like a good idea to me. >>>>>>>> Remko >>>>>>>> >>>>>>>> Sent from my iPhone >>>>>>>> >>>>>>>>> On Jan 15, 2017, at 12:26, Apache <ralph.go...@dslextreme.com> wrote: >>>>>>>>> >>>>>>>>> Fine by me. >>>>>>>>> >>>>>>>>> Ralph >>>>>>>>> >>>>>>>>>> On Jan 14, 2017, at 8:19 PM, Matt Sicker <boa...@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>> http://apache.org/dev/svngit2jira.html >>>>>>>>>> >>>>>>>>>> Basically, this would work similarly to how the current GitHub >>>>>>>>>> integration works where comments made on pull requests get >>>>>>>>>> cross-posted to jira. This other integration would cross-post >>>>>>>>>> commits that make jira references since we don't use Bitbucket or >>>>>>>>>> anything like that. >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Matt Sicker <boa...@gmail.com> >>>>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matt Sicker <boa...@gmail.com> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matt Sicker <boa...@gmail.com> >>>> >>>> >>>> >>>> -- >>>> >>>> >>>> Mikael Ståldal >>>> Senior software developer >>>> >>>> Magine TV >>>> mikael.stal...@magine.com >>>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >>>> >>>> Privileged and/or Confidential Information may be contained in this >>>> message. If you are not the addressee indicated in this message >>>> (or responsible for delivery of the message to such a person), you may not >>>> copy or deliver this message to anyone. In such case, >>>> you should destroy this message and kindly notify the sender by reply >>>> email. >> >> >> >> -- >> Matt Sicker <boa...@gmail.com> > > > > -- > Matt Sicker <boa...@gmail.com>
