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

Dima Spivak commented on HBASE-15119:
-------------------------------------

Oy. Damn you, JIRA. I meant that having {code}${COMMIT[1]}/${SHA[1]}{code}would 
have the same effect (albeit with a hanging slash at the end if the variable 
were missing).

> Include git SHA in check_compatibility reports
> ----------------------------------------------
>
>                 Key: HBASE-15119
>                 URL: https://issues.apache.org/jira/browse/HBASE-15119
>             Project: HBase
>          Issue Type: Improvement
>          Components: build
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15119.v00.patch
>
>
> Since some refs change over time (ie, branches), it would be nice to include 
> git shas in the version info included in check compatibility reports. It'll 
> also help interested parties to be sure of what they're looking at.



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

Reply via email to