diff options
Diffstat (limited to 'man1/git-request-pull.1')
| -rw-r--r-- | man1/git-request-pull.1 | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/man1/git-request-pull.1 b/man1/git-request-pull.1 index cc444585a..9b3297ea9 100644 --- a/man1/git-request-pull.1 +++ b/man1/git-request-pull.1 @@ -2,12 +2,12 @@ .\" Title: git-request-pull .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author] .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/> -.\" Date: 2023-10-20 +.\" Date: 2023-10-23 .\" Manual: Git Manual -.\" Source: Git 2.42.0.424.gceadf0f3cf +.\" Source: Git 2.42.0.482.g2e8e77cbac .\" Language: English .\" -.TH "GIT\-REQUEST\-PULL" "1" "2023\-10\-20" "Git 2\&.42\&.0\&.424\&.gceadf0" "Git Manual" +.TH "GIT\-REQUEST\-PULL" "1" "2023\-10\-23" "Git 2\&.42\&.0\&.482\&.g2e8e77" "Git Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -37,7 +37,7 @@ git-request-pull \- Generates a summary of pending changes .sp .SH "DESCRIPTION" .sp -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\&. +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\&. .sp 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\&. .SH "OPTIONS" @@ -70,7 +70,7 @@ syntax, to have its local name, a colon .RE .SH "EXAMPLES" .sp -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: +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 into the project\&. First you push that change to your public repository for others to see: .sp .if n \{\ .RS 4 |