diff options
Diffstat (limited to 'man1/git-format-patch.1')
-rw-r--r-- | man1/git-format-patch.1 | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/man1/git-format-patch.1 b/man1/git-format-patch.1 index 334aad395..dddea66dc 100644 --- a/man1/git-format-patch.1 +++ b/man1/git-format-patch.1 @@ -2,12 +2,12 @@ .\" Title: git-format-patch .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author] .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/> -.\" Date: 2024-02-06 +.\" Date: 2024-02-08 .\" Manual: Git Manual -.\" Source: Git 2.43.0.561.g235986be82 +.\" Source: Git 2.43.0.581.g5216f8f5c4 .\" Language: English .\" -.TH "GIT\-FORMAT\-PATCH" "1" "2024\-02\-06" "Git 2\&.43\&.0\&.561\&.g235986" "Git Manual" +.TH "GIT\-FORMAT\-PATCH" "1" "2024\-02\-08" "Git 2\&.43\&.0\&.581\&.g5216f8" "Git Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -40,10 +40,10 @@ git-format-patch \- Prepare patches for e\-mail submission [\-\-signature\-file=<file>] [\-n | \-\-numbered | \-N | \-\-no\-numbered] [\-\-start\-number <n>] [\-\-numbered\-files] - [\-\-in\-reply\-to=<message id>] [\-\-suffix=\&.<sfx>] + [\-\-in\-reply\-to=<message\-id>] [\-\-suffix=\&.<sfx>] [\-\-ignore\-if\-in\-upstream] [\-\-always] [\-\-cover\-from\-description=<mode>] - [\-\-rfc] [\-\-subject\-prefix=<subject prefix>] + [\-\-rfc] [\-\-subject\-prefix=<subject\-prefix>] [(\-\-reroll\-count|\-v) <n>] [\-\-to=<email>] [\-\-cc=<email>] [\-\-[no\-]cover\-letter] [\-\-quiet] @@ -53,8 +53,8 @@ git-format-patch \- Prepare patches for e\-mail submission [\-\-range\-diff=<previous> [\-\-creation\-factor=<percent>]] [\-\-filename\-max\-length=<n>] [\-\-progress] - [<common diff options>] - [ <since> | <revision range> ] + [<common\-diff\-options>] + [ <since> | <revision\-range> ] .fi .sp .SH "DESCRIPTION" @@ -124,7 +124,7 @@ A single commit, <since>, specifies that the commits leading to the tip of the c .sp -1 .IP " 2." 4.2 .\} -Generic <revision range> expression (see "SPECIFYING REVISIONS" section in +Generic <revision\-range> expression (see "SPECIFYING REVISIONS" section in \fBgitrevisions\fR(7)) means the commits in the specified range\&. .RE .sp @@ -339,7 +339,7 @@ Synonym for \-\-dirstat=cumulative .PP \-\-dirstat\-by\-file[=<param1,param2>\&...] .RS 4 -Synonym for \-\-dirstat=files,param1,param2\&... +Synonym for \-\-dirstat=files,<param1>,<param2>\&... .RE .PP \-\-summary @@ -753,10 +753,10 @@ to take care of threading, you will want to ensure that threading is disabled fo \fBgit send\-email\fR\&. .RE .PP -\-\-in\-reply\-to=<message id> +\-\-in\-reply\-to=<message\-id> .RS 4 Make the first mail (or all the mails with -\fB\-\-no\-thread\fR) appear as a reply to the given <message id>, which avoids breaking threads to provide a new patch series\&. +\fB\-\-no\-thread\fR) appear as a reply to the given <message\-id>, which avoids breaking threads to provide a new patch series\&. .RE .PP \-\-ignore\-if\-in\-upstream @@ -804,12 +804,12 @@ is Use the contents of <file> instead of the branch\(cqs description for generating the cover letter\&. .RE .PP -\-\-subject\-prefix=<subject prefix> +\-\-subject\-prefix=<subject\-prefix> .RS 4 Instead of the standard \fI[PATCH]\fR prefix in the subject line, instead use -\fI[<subject prefix>]\fR\&. This can be used to name a patch series, and can be combined with the +\fI[<subject\-prefix>]\fR\&. This can be used to name a patch series, and can be combined with the \fB\-\-numbered\fR option\&. .sp @@ -1023,7 +1023,7 @@ configuration\&. .PP \-\-root .RS 4 -Treat the revision argument as a <revision range>, even if it is just a single commit (that would normally be treated as a <since>)\&. Note that root commits included in the specified range are always formatted as creation patches, independently of this flag\&. +Treat the revision argument as a <revision\-range>, even if it is just a single commit (that would normally be treated as a <since>)\&. Note that root commits included in the specified range are always formatted as creation patches, independently of this flag\&. .RE .PP \-\-progress |