Re: Branch update merge blizzards

: Is there some specific intent why there should be commit-level email for a : mere non-release branch update? I mean, does anybody get any value from : them? I do want to see them if master or branch_xy gets merged into, but : not for branches LUCENE/SOLR-, especially when each of those Jira

Re: Branch update merge blizzards

On 3/11/2016 5:50 PM, Jack Krupansky wrote: > I was curious if there was a specific intentional reason for some of > the git commit email that seems to come as a blizzard of like 50 > messages whenever somebody simply updates a work in progress branch > and doesn't seem related to an actual commit

Re: Branch update merge blizzards

I hear ya Jack; it sucks. We filled an issue already, at least as far as the git JIRA commit bot: https://issues.apache.org/jira/browse/INFRA-11198 ~ David On Fri, Mar 11, 2016 at 7:55 PM Jack Krupansky wrote: > I was curious if there was a specific intentional reason

Branch update merge blizzards

I was curious if there was a specific intentional reason for some of the git commit email that seems to come as a blizzard of like 50 messages whenever somebody simply updates a work in progress branch and doesn't seem related to an actual commit to a release branch. The latest just now was