"W. Trevor King" <wking@xxxxxxxxxx> writes: > From: "W. Trevor King" <wking@xxxxxxxxxx> > > 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@xxxxxxxxxx> > --- > Documentation/user-manual.txt | 11 +++-------- > 1 file changed, 3 insertions(+), 8 deletions(-) > > diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt > index d9276d7..cf09ddf 100644 > --- a/Documentation/user-manual.txt > +++ b/Documentation/user-manual.txt > @@ -2304,16 +2304,11 @@ 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]: The command you refer to does the _whole_ thing, not just to create diffstat and shortlog summaries to be included. > ------------------------------------------------- > +$ git push mytree > +$ git request-pull origin mytree release > ------------------------------------------------- The introductory text to tell the reader what they are being taught needs to be updated a bit more, I think. After pushing your work to "mytree", you can use request-pull command to prepare a "please pull" request message to send to Linus, like so: or something. > > Here are some of the scripts that simplify all this even further. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html