[
https://issues.apache.org/jira/browse/HBASE-15017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066022#comment-15066022
]
Sean Busbey commented on HBASE-15017:
-------------------------------------
for whatever reason, I can't get git on windows to generate a patch for the
empty commit. Here's the commit message I plan to include, if someone wouldn't
mind providing a review based on it. I think it gets all of the PRs that aren't
likely to be followed up via jira:
{code}
commit 9bbf43b0bc6fb13ccc42e001b638394165a3f0b3
Author: Sean Busbey <[email protected]>
Date: Sun Dec 20 20:11:12 2015 -0600
HBASE-15017 Clean up stale github PRs.
* closes #10 (already applied via jira)
* closes #23 (attempts merge branch-1.1 -> master)
* closes #2 (attempts merge 0.94 -> master)
{code}
> Close out GitHub pull requests that aren't likely to update into a usable
> patch
> -------------------------------------------------------------------------------
>
> Key: HBASE-15017
> URL: https://issues.apache.org/jira/browse/HBASE-15017
> Project: HBase
> Issue Type: Task
> Components: community
> Reporter: Sean Busbey
> Assignee: Sean Busbey
>
> We have a bunch of open github PRs. Some of them might turn into things we
> can close as a part of pushing a fix; mostly they're just missing a jira
> because folks showed up at github first.
> Others look like mistaken pull requests or are things we've already pushed
> but without noting it.
> To clean up the latter, we should push an empty commit that says it closes
> the issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
