user-manual: Use request-pull to generate "please pull" text
Less work and more error checking (e.g. does a merge base exist?). Add an explicit push before request-pull to satisfy request-pull, which checks to make sure the references are publically available. Signed-off-by: W. Trevor King <wking@tremily.us> Signed-off-by: Junio C Hamano <gitster@pobox.com>
W. Trevor King committed
Feb 19, 2013 at 05:05 UTC
ae6ef554c8c785f96fce482e33cc78080aafc43f
1 file changed
+5
-9
Documentation/user-manual.txt
+5
-9
@@ -2305,17 +2305,13 @@ branch and then merge into each of the test and release branches. For
2305
these changes, just apply directly to the "release" branch, and then
2306
merge that into the "test" branch.
2307
2308
-To create diffstat and shortlog summaries of changes to include in a "please
2309
-pull" request to Linus you can use:
2308
+After pushing your work to `mytree`, you can use
2309
+linkgit:git-request-pull[1] to prepare a "please pull" request message
2310
+to send to Linus:
2311
2312
-------------------------------------------------
2312
-$ git diff --stat origin..release
2313
--------------------------------------------------
2314
-
2315
-and
2316
-
2317
--------------------------------------------------
2318
-$ git log -p origin..release | git shortlog
2313
+$ git push mytree
2314
+$ git request-pull origin mytree release
2315
-------------------------------------------------
2316
2317
Here are some of the scripts that simplify all this even further.