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 Thu, 31 Jan 2019 22:05:00 GMT

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

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

I see this is marked waiting for user, Not sure what you are waiting for... from my perspective
(others may have a different opinion) it's not the size of the email that matters it's the
fact I have to read the title and decide if I want to open it. Just handling the sheer number
of emails is what bogs me down. 

> 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