hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-15909) Use Yetus' patch naming rules in submit-patch.py
Date Sun, 29 May 2016 04:56:12 GMT

     [ https://issues.apache.org/jira/browse/HBASE-15909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-15909:
--------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.0.0
           Status: Resolved  (was: Patch Available)

Lets try it, Pushed to master. Thanks [~appy]

> Use Yetus' patch naming rules in submit-patch.py
> ------------------------------------------------
>
>                 Key: HBASE-15909
>                 URL: https://issues.apache.org/jira/browse/HBASE-15909
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Appy
>            Assignee: Appy
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15909.master.001.patch, HBASE-15909.master.002.patch
>
>
> Rules are here: https://yetus.apache.org/contribute/
> Naming convention is: (JIRA).(branch name).(patch number).patch
> Pre-submit was not able to deduce the branch from old names being generated by this script
(so defaulted back to master everytime).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message