Skip to content

Commit ae6ef55

Browse files
wkinggitster
authored andcommitted
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 6c26bf4 commit ae6ef55

File tree

1 file changed

+5
-9
lines changed

1 file changed

+5
-9
lines changed

Documentation/user-manual.txt

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2305,17 +2305,13 @@ branch and then merge into each of the test and release branches. For
23052305
these changes, just apply directly to the "release" branch, and then
23062306
merge that into the "test" branch.
23072307

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:
23102311

23112312
-------------------------------------------------
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
23192315
-------------------------------------------------
23202316

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

0 commit comments

Comments
 (0)