Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- All guides...
- 2.35.1 → 2.41.0 no changes
- 2.35.0 01/24/22
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.
The upstream project is expected to have the commit named by
<start> and the output asks it to integrate the changes you made
since that commit, up to the commit named by
<end>, by visiting
the repository named by
Include patch text in the output.
Commit to start at. This names a commit that is already in the upstream history.
The repository URL to be pulled from.
Commit to end at (defaults to HEAD). This names the commit at the tip of the history you are asking to be pulled.
When the repository named by
<url>has the commit at a tip of a ref that is different from the ref you have locally, you can use the
<local>:<remote>syntax, to have its local name, a colon
:, and its remote name.
Imagine that you built your work on your
master branch on top of
v1.0 release, and want it to be integrated to the project.
First you push that change to your public repository for others to
git push https://git.ko.xz/project master
Then, you run this command:
git request-pull v1.0 https://git.ko.xz/project master
which will produce a request to the upstream, summarizing the
changes between the
v1.0 release and your
master, to pull it
from your public repository.
If you pushed your change to a branch whose name is different from the one you have locally, e.g.
git push https://git.ko.xz/project master:for-linus
then you can ask that to be pulled with
git request-pull v1.0 https://git.ko.xz/project master:for-linus
Part of the git suite