2 .\" Title: git-request-pull
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
7 .\" Source: Git 2.35.1.225.ge2ac9141e6
10 .TH "GIT\-REQUEST\-PULL" "1" "02/17/2022" "Git 2\&.35\&.1\&.225\&.ge2ac91" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 git-request-pull \- Generates a summary of pending changes
35 \fIgit request\-pull\fR [\-p] <start> <URL> [<end>]
40 Generate a request asking your upstream project to pull changes into their tree\&. The request, printed to the standard output, begins with the branch description, summarizes the changes and indicates from where they can be pulled\&.
42 The upstream project is expected to have the commit named by \fB<start>\fR and the output asks it to integrate the changes you made since that commit, up to the commit named by \fB<end>\fR, by visiting the repository named by \fB<URL>\fR\&.
47 Include patch text in the output\&.
52 Commit to start at\&. This names a commit that is already in the upstream history\&.
57 The repository URL to be pulled from\&.
62 Commit to end at (defaults to HEAD)\&. This names the commit at the tip of the history you are asking to be pulled\&.
64 When the repository named by
66 has the commit at a tip of a ref that is different from the ref you have locally, you can use the
67 \fB<local>:<remote>\fR
68 syntax, to have its local name, a colon
69 \fB:\fR, and its remote name\&.
73 Imagine that you built your work on your \fBmaster\fR branch on top of the \fBv1\&.0\fR release, and want it to be integrated to the project\&. First you push that change to your public repository for others to see:
79 git push https://git\&.ko\&.xz/project master
85 Then, you run this command:
91 git request\-pull v1\&.0 https://git\&.ko\&.xz/project master
97 which will produce a request to the upstream, summarizing the changes between the \fBv1\&.0\fR release and your \fBmaster\fR, to pull it from your public repository\&.
99 If you pushed your change to a branch whose name is different from the one you have locally, e\&.g\&.
105 git push https://git\&.ko\&.xz/project master:for\-linus
111 then you can ask that to be pulled with
117 git request\-pull v1\&.0 https://git\&.ko\&.xz/project master:for\-linus
124 Part of the \fBgit\fR(1) suite