Re: [PATCH v2 12/15] user-manual: Use request-pull to generate "please pull" text
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:56:06
"W. Trevor King" [off-list ref] writes:
quoted hunk
From: "W. Trevor King" <redacted> Less work and more error checking (e.g. does a merge base exist?). Signed-off-by: W. Trevor King <redacted> --- Documentation/user-manual.txt | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-)diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 31054a2..6446791 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt@@ -2298,17 +2298,14 @@ 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: +pull" request to Linus you can use linkgit:git-request-pull[1]: ------------------------------------------------- -$ git diff --stat origin..release +$ git request-pull origin git://example.com/proj.git release ------------------------------------------------- -and - -------------------------------------------------- -$ git log -p origin..release | git shortlog -------------------------------------------------- +where the `git://` URL points to your <<public-repositories,public +repository>>. Here are some of the scripts that simplify all this even further.
The request-pull checks a lot more than "does a merge base exist?", no? Does the examples in this flow push out what you want to be pulled _before_ running this step?