[
https://issues.apache.org/jira/browse/HBASE-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179637#comment-14179637
]
Hudson commented on HBASE-12249:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #5685 (See
[https://builds.apache.org/job/HBase-TRUNK/5685/])
HBASE-12249 Addendum - Convert tabs to spaces (mstanleyjones: rev
dfa98ab93b9e6d444a56c5a7fad7bf05cd3d790e)
* dev-support/make_patch.sh
> Script to help you adhere to the patch-naming guidelines
> --------------------------------------------------------
>
> Key: HBASE-12249
> URL: https://issues.apache.org/jira/browse/HBASE-12249
> Project: HBase
> Issue Type: Improvement
> Components: documentation, scripts
> Reporter: Misty Stanley-Jones
> Assignee: Misty Stanley-Jones
> Priority: Minor
> Fix For: 2.0.0, 0.99.2
>
> Attachments: HBASE-12249-v1.patch, HBASE-12249-v2-addendum.patch,
> HBASE-12249-v2.patch, HBASE-12249.patch
>
>
> I wrote a script to help me name patches correctly, and it may be helpful to
> others. You use it from the branch where you are working, and it looks in
> your patches directory to see if other versions of the patch exist, and
> appends -v<latest+1> if so. If you specify -a, it creates an addendum patch,
> by appending -v<latest>-addendum.
> In summary, it makes patches named like:
> HBASE-XXXX.patch
> HBASE-XXXX-vY.patch
> HBASE-XXXX-addendum.patch
> HBASE-XXXX-vY-addendum.patch
> The patch uses git format-patch if you have only one local commit, otherwise
> lets you rebase or use git diff. It does not use --no-prefix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)