infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17771) Move to Gitbox seems to have undone INFRA-11198
Date Sun, 03 Feb 2019 05:01:00 GMT

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

David Smiley commented on INFRA-17771:
--------------------------------------

I definitely concur with Gus.  I suppose a work-round is to possibly avoid branches on the
primary repo, and instead push to a fork (likely a branch there but wouldn't get the email).
 It's only when multiple people want to push to a branch where we do it on the primary repo
due to convenience of collaboration.

> 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