[
https://issues.apache.org/jira/browse/HBASE-19098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-19098:
-----------------------------------
Description: 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. (was: 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 the upstream be named "origin" could be
removed, that would be good, or otherwise this should be documented next to the
example usage in the python source. )
> 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
>
> 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)
