infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gus Heck (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17771) Move to Gitbox seems to have undone INFRA-11198
Date Tue, 12 Feb 2019 06:59:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-17771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765739#comment-16765739
] 

Gus Heck commented on INFRA-17771:
----------------------------------

Looking again I think I confused two things... The jira comments (that then generate emails)
and the direct commit emails. I had had the impression from a prior communication that the
pattern matching prevented the commit mails directly but maybe that's not the case, maybe
it was just the jira based emails. So now I'm not sure if this really has changed or not.
Now that I look at it from that angle, I've not found cases of "dupllicate hashes" in jira
comments, merely several commit emails on the list, which I had not expected when I committed
to my branch matching the pattern.

So I guess maybe it's a different symptom that I've observed, and it's "problem" status is
debatable (still not useful emails for most of the rest of the world, but not spamming jira,
and easily labeled as a commit mail). I will have to pay attention to what happens with jira
when I merge in my branch. 

> Move to Gitbox seems to have undone INFRA-11198
> -----------------------------------------------
>
>                 Key: INFRA-17771
>                 URL: https://issues.apache.org/jira/browse/INFRA-17771
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: GitBox
>            Reporter: Gus Heck
>            Assignee: Daniel Gruno
>            Priority: Minor
>
> INFRA-11198 established a pattern (prefix) for branch names such that commits on branches
matching that prefix that would not be reported to the mailing list.  The intent was that
long lived branches being updated to master would not spam the list re-posting past commit
messages when the branch is updated to master (or other parent). 
> I attempted to utilize that pattern ( {{(lucene|solr).*}} )  today when I created a branch
named solr-13131 for work on CategoryRoutedAliases (SOLR-13131), but I still see messages
being sent to the list regarding commits on my feature branch. I suspect this feature was
not carried forward to the new gitbox based repository.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message