Skip to content

Commit

Permalink
user-manual: Use request-pull to generate "please pull" text
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
W. Trevor King authored and Junio C Hamano committed Feb 19, 2013
1 parent 6c26bf4 commit ae6ef55
Showing 1 changed file with 5 additions and 9 deletions.
14 changes: 5 additions & 9 deletions Documentation/user-manual.txt
Original file line number Diff line number Diff line change
Expand Up @@ -2305,17 +2305,13 @@ branch and then merge into each of the test and release branches. For
these changes, just apply directly to the "release" branch, and then
merge that into the "test" branch.

To create diffstat and shortlog summaries of changes to include in a "please
pull" request to Linus you can use:
After pushing your work to `mytree`, you can use
linkgit:git-request-pull[1] to prepare a "please pull" request message
to send to Linus:

-------------------------------------------------
$ git diff --stat origin..release
-------------------------------------------------

and

-------------------------------------------------
$ git log -p origin..release | git shortlog
$ git push mytree
$ git request-pull origin mytree release
-------------------------------------------------

Here are some of the scripts that simplify all this even further.
Expand Down

0 comments on commit ae6ef55

Please sign in to comment.