You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2017/10/26 20:25:00 UTC

[jira] [Commented] (HBASE-19098) Python based compatiblity checker fails if git repo does not have a remote named 'origin'

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

Andrew Purtell commented on HBASE-19098:
----------------------------------------

+1

Thanks.


> Python based compatiblity checker fails if git repo does not have a remote named 'origin'
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-19098
>                 URL: https://issues.apache.org/jira/browse/HBASE-19098
>             Project: HBase
>          Issue Type: Bug
>          Components: tooling
>            Reporter: Andrew Purtell
>            Assignee: Sean Busbey
>            Priority: Critical
>         Attachments: HBASE-19098.0.patch
>
>
> The new Python based compatibility checker will fail if the local git repo does not have a remote named "origin". I develop with multiple upstream repos and rename them according to a custom convention. If the requirement that an upstream named "origin" must be present could be removed, that would be good, or otherwise this should be documented next to the example usage in the python source. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)