[
https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759742#comment-13759742
]
Nick Dimiduk commented on HBASE-9153:
-------------------------------------
bq. You can have two references from the same git repo, but you'd have to
specify it twice, once as argument $1 and once as argument $3.
Yeah, that's what I figured. It would be nice to not have to checkout fresh
repos from a remote repository twice. hbase.git is a 150mb repo, which can be
slow over a slow link.
Yep, 28 minutes is what it took here. The report looks as correct as I can
tell. Good job!
> Create a deprecation policy enforcement check
> ---------------------------------------------
>
> Key: HBASE-9153
> URL: https://issues.apache.org/jira/browse/HBASE-9153
> Project: HBase
> Issue Type: Task
> Reporter: Jonathan Hsieh
> Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch,
> HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch
>
>
> We've had a few issues now where we've removed API's without deprecating or
> deprecating in the late release. (HBASE-9142, HBASE-9093) We should just
> have a tool that enforces our api deprecation policy as a release time check
> or as a precommit check.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
