Add git cherry picking extension

man/src/git-cherry-pick-upload.txt

Index: man/src/git-cherry-pick-upload.txt
diff --git a/man/src/git-cherry-pick-upload.txt b/man/src/git-cherry-pick-upload.txt
new file mode 100644
index 0000000000000000000000000000000000000000..f4908b82923101cb4c7d447c161d60b47ba4b2e6
--- /dev/null
+++ b/man/src/git-cherry-pick-upload.txt
@@ -0,0 +1,35 @@
+git-cherry-pick-upload(1)
+=============
+
+NAME
+----
+git-cherry-pick-upload -
+include::_git-cherry-pick-upload_desc.helper.txt[]
+
+SYNOPSIS
+--------
+[verse]
+'git cherry-pick-upload'

[iannucci, 2014/07/29 18:41:35]

should have example options here, probably -b <local_branch_ref>
<hash_to_cherry_pick>

[smut, 2014/07/29 22:15:44]

Done.

+
+DESCRIPTION
+-----------
+
+`git cherry-pick-upload` is used to upload a cherry pick to rietveld. It uses
+your view of the remote to generate the diff between a revision and its parent,
+and then uploads that diff to rietveld.

[iannucci, 2014/07/29 18:41:35]

This paragraph is confusing. I think you mean 

It cherry-picks '<hash>' onto the specified branch, using your local clone's
state of the branch. Because of this, make your local branch ref is up-to-date
(using git-fetch) before using this command. Otherwise the CL that this uploads
may not apply cleanly to the branch when you try to land it.

mebbeh?

[smut, 2014/07/29 22:15:44]

It doesn't cherry pick the hash onto anything. It finds the parent of the hash,
generates the diff, and uploads that diff to rietveld with a modified 'project'
parameter.

+
+The commit message is annotated with "(cherry picked from commit [parent sha1])"
+as if it were generated by `git cherry-pick -x`.
+
+EXAMPLE
+-------
+demo:1[]
+
+SEE ALSO
+--------
+linkgit:git-cherry-pick[1]
+linkgit:git-cl-upload[1]
+
+include::_footer.txt[]
+
+// vim: ft=asciidoc: