[
https://issues.apache.org/jira/browse/HBASE-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-12249:
----------------------------------------
Attachment: HBASE-12249-v2.patch
This patch includes some style improvements, checks to see if your local
directory is dirty (has uncommitted changes), and accepts a patch directory as
an argument (-d <directory>). If you don't specify a directory, it falls back
to ~patches. It also creates the patch directory if necessary. If accepted,
I'll update the necessary docs on commit.
[~dimaspivak] and others feedback appreciated.
> 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
> Attachments: HBASE-12249-v1.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)
