mirror of
https://github.com/git/git
synced 2024-10-29 17:08:46 +00:00
76a8788c14
When formatted as a man page, 1st section header is always in upper case even if we write it otherwise. Make all 1st section headers uppercase to keep it close to the final output. This does affect html since case is kept there, but I still think it's a good idea to maintain a consistent style for 1st section headers. Some sections perhaps should become second sections instead, where case is kept, and for better organization. I will update if anyone has suggestions about this. While at there I also make some header more consistent (e.g. examples vs example) and fix a couple minor things here and there. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
79 lines
2 KiB
Text
79 lines
2 KiB
Text
git-request-pull(1)
|
|
===================
|
|
|
|
NAME
|
|
----
|
|
git-request-pull - Generates a summary of pending changes
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'git request-pull' [-p] <start> <url> [<end>]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
|
|
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 `<url>`.
|
|
|
|
|
|
OPTIONS
|
|
-------
|
|
-p::
|
|
Include patch text in the output.
|
|
|
|
<start>::
|
|
Commit to start at. This names a commit that is already in
|
|
the upstream history.
|
|
|
|
<url>::
|
|
The repository URL to be pulled from.
|
|
|
|
<end>::
|
|
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.
|
|
|
|
|
|
EXAMPLES
|
|
--------
|
|
|
|
Imagine that you built your work on your `master` branch on top of
|
|
the `v1.0` release, and want it to be integrated to the project.
|
|
First you push that change to your public repository for others to
|
|
see:
|
|
|
|
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
|
|
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|