Branch update merge blizzards

[Jack Krupansky <ja...@gmail.com>]

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 related to "SOLR-445: Merge remote-tracking branch
'origin' into jira/SOLR-445"

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-nnnn, especially when each of those Jira
issues needs the same merge updates.

Just curious.

-- Jack Krupansky

Re: Branch update merge blizzards

[David Smiley <da...@gmail.com>]

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 <ja...@gmail.com>
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 to a release branch.
>
> The latest just now was related to "SOLR-445: Merge remote-tracking branch
> 'origin' into jira/SOLR-445"
>
> 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-nnnn, especially when each of those Jira
> issues needs the same merge updates.
>
> Just curious.
>
> -- Jack Krupansky
>
-- 
Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
http://www.solrenterprisesearchserver.com

Re: Branch update merge blizzards

[Chris Hostetter <ho...@fucit.org>]

: 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-nnnn, especially when each of those Jira
: issues needs the same merge updates.

part of the issue is just the generalization of how the tools work -- 
branches that are important to some people are unimportant to tohers, and 
the commit notification email code doesn't really know which are which, so 
it does the same thing for every branch.

As discussed in another thread last month, i've filed an issue with INFRA 
to request that the details of what branch is being updated be included in 
every email subject...

	https://issues.apache.org/jira/browse/INFRA-11462

...so ideally, moving forward, you can tell at a glance which commits are 
to feature branches vs "master" or bug fix branches (or have your email 
client filter/flag the ones you do/don't care about) ... even if a single 
push contains multiple commits to multiple branches.


-Hoss
http://www.lucidworks.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org

Re: Branch update merge blizzards

[Shawn Heisey <ap...@elyograg.org>]

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 to a release branch.
>
> The latest just now was related to "SOLR-445: Merge remote-tracking
> branch 'origin' into jira/SOLR-445"

I wouldn't mind seeing a single summary message for commits to ancillary
branches.  If the info can't fit into a single message, include a link
for interested parties.  I definitely do not need a 50 message storm. 
Such a storm is a lot of work for my mail server, though it's never
complained.  The *thousands* of messages generated on ASF's mail servers
would have the potential to cause significant delays to more important
mail traffic.

I think it could be argued that such an email storm is unnecessary even
for the primary branches.  I almost never look deeper than the first
message on something like that ... and if I really *am* interested, the
web-based access to git is probably a better way to examine the commit
anyway.

Jira is down so I can't look at the issue David referenced.  I will look
later.

Thanks,
Shawn


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org