From: Junio C Hamano Date: Sun, 10 Feb 2013 22:23:48 GMT Subject: Re: [PATCH v2 12/15] user-manual: Use request-pull to generate "please pull" text Message-ID: <7vehgnst8r.fsf@alter.siamese.dyndns.org> In-Reply-To: <3d860e7c19b33ebc2725eb86ec481f966e3007de.1360508415.git.wking@tremily.us> "W. Trevor King" writes: > From: "W. Trevor King" > > Less work and more error checking (e.g. does a merge base exist?). > > Signed-off-by: W. Trevor King > --- > 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 < +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?