[
https://issues.apache.org/jira/browse/HBASE-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170345#comment-14170345
]
Elliott Clark commented on HBASE-12249:
---------------------------------------
I'd personally much rather have git-format-patch though. That way I can give a
user credit for their commit.
> 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
>
> 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 diff, and does not use --no-prefix. It does not use git
> format-patch because it's too hard to programmatically squash commits and
> reword commit messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
