blob: c32cb0bea1d6c057dabdd3065417744f5209ba46 [file] [log] [blame]
Junio C Hamano215a7ad2005-09-07 17:26:23 -07001git-request-pull(1)
2===================
Junio C Hamano7fc9d692005-08-23 01:49:47 -07003
4NAME
5----
Fredrik Kuivinen7bd7f282006-03-09 17:24:50 +01006git-request-pull - Generates a summary of pending changes
Junio C Hamano7fc9d692005-08-23 01:49:47 -07007
8SYNOPSIS
9--------
Martin von Zweigbergk7791a1d2011-07-01 22:38:26 -040010[verse]
Stephen Boydd8e3ac72010-07-23 09:31:27 -070011'git request-pull' [-p] <start> <url> [<end>]
Junio C Hamano7fc9d692005-08-23 01:49:47 -070012
13DESCRIPTION
14-----------
Junio C Hamano7fc9d692005-08-23 01:49:47 -070015
Junio C Hamanoec445072014-03-12 11:04:11 -070016Generate a request asking your upstream project to pull changes into
Philip Oakley561d2b72015-09-14 15:10:53 +010017their tree. The request, printed to the standard output,
18begins with the branch description, summarizes
Junio C Hamanoec445072014-03-12 11:04:11 -070019the changes and indicates from where they can be pulled.
20
21The upstream project is expected to have the commit named by
22`<start>` and the output asks it to integrate the changes you made
23since that commit, up to the commit named by `<end>`, by visiting
24the repository named by `<url>`.
25
Junio C Hamano7fc9d692005-08-23 01:49:47 -070026
27OPTIONS
28-------
Stephen Boydd8e3ac72010-07-23 09:31:27 -070029-p::
Junio C Hamanoec445072014-03-12 11:04:11 -070030 Include patch text in the output.
Stephen Boydd8e3ac72010-07-23 09:31:27 -070031
A Large Angry SCMb5dca4b2005-08-29 22:33:14 -040032<start>::
Junio C Hamanoec445072014-03-12 11:04:11 -070033 Commit to start at. This names a commit that is already in
34 the upstream history.
Junio C Hamano7fc9d692005-08-23 01:49:47 -070035
A Large Angry SCMb5dca4b2005-08-29 22:33:14 -040036<url>::
Junio C Hamanoec445072014-03-12 11:04:11 -070037 The repository URL to be pulled from.
Junio C Hamano7fc9d692005-08-23 01:49:47 -070038
A Large Angry SCMb5dca4b2005-08-29 22:33:14 -040039<end>::
Junio C Hamanoec445072014-03-12 11:04:11 -070040 Commit to end at (defaults to HEAD). This names the commit
41 at the tip of the history you are asking to be pulled.
42+
43When the repository named by `<url>` has the commit at a tip of a
44ref that is different from the ref you have locally, you can use the
45`<local>:<remote>` syntax, to have its local name, a colon `:`, and
46its remote name.
47
48
49EXAMPLE
50-------
51
52Imagine that you built your work on your `master` branch on top of
53the `v1.0` release, and want it to be integrated to the project.
54First you push that change to your public repository for others to
55see:
56
57 git push https://git.ko.xz/project master
58
59Then, you run this command:
60
61 git request-pull v1.0 https://git.ko.xz/project master
62
63which will produce a request to the upstream, summarizing the
64changes between the `v1.0` release and your `master`, to pull it
65from your public repository.
66
67If you pushed your change to a branch whose name is different from
68the one you have locally, e.g.
69
70 git push https://git.ko.xz/project master:for-linus
71
72then you can ask that to be pulled with
73
74 git request-pull v1.0 https://git.ko.xz/project master:for-linus
75
Junio C Hamano7fc9d692005-08-23 01:49:47 -070076
Junio C Hamano7fc9d692005-08-23 01:49:47 -070077GIT
78---
Christian Couder9e1f0a82008-06-06 09:07:32 +020079Part of the linkgit:git[1] suite