diff options
Diffstat (limited to 'man1/git-bundle.1')
| -rw-r--r-- | man1/git-bundle.1 | 27 |
1 files changed, 10 insertions, 17 deletions
diff --git a/man1/git-bundle.1 b/man1/git-bundle.1 index a0d03a90e..39c4a3cc9 100644 --- a/man1/git-bundle.1 +++ b/man1/git-bundle.1 @@ -2,12 +2,12 @@ .\" Title: git-bundle .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author] .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/> -.\" Date: 08/12/2022 +.\" Date: 08/18/2022 .\" Manual: Git Manual -.\" Source: Git 2.37.2.324.gafa70145a2 +.\" Source: Git 2.37.2.382.g795ea8776b .\" Language: English .\" -.TH "GIT\-BUNDLE" "1" "08/12/2022" "Git 2\&.37\&.2\&.324\&.gafa701" "Git Manual" +.TH "GIT\-BUNDLE" "1" "08/18/2022" "Git 2\&.37\&.2\&.382\&.g795ea8" "Git Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -58,7 +58,7 @@ Bundles created using revision exclusions are "thin packs" created using the \fB .sp There is no option to create a "thick pack" when using revision exclusions, and users should not be concerned about the difference\&. By using "thin packs", bundles created using exclusions are smaller in size\&. That they\(cqre "thin" under the hood is merely noted here as a curiosity, and as a reference to other documentation\&. .sp -See \m[blue]\fBthe \fBbundle\-format\fR documentation\fR\m[]\&\s-2\u[1]\d\s+2 for more details and the discussion of "thin pack" in \m[blue]\fBthe pack format documentation\fR\m[]\&\s-2\u[2]\d\s+2 for further details\&. +See \fBgitformat-bundle\fR(5) for more details and the discussion of "thin pack" in \fBgitformat-pack\fR(5) for further details\&. .SH "OPTIONS" .PP create [options] <file> <git\-rev\-list\-args> @@ -77,7 +77,9 @@ verify <file> .RS 4 Used to check that a bundle file is valid and will apply cleanly to the current repository\&. This includes checks on the bundle format itself as well as checking that the prerequisite commits exist and are fully linked in the current repository\&. Then, \fIgit bundle\fR -prints a list of missing commits, if any\&. Finally, information about additional capabilities, such as "object filter", is printed\&. See "Capabilities" in link:technical/bundle\-format\&.html for more information\&. The exit code is zero for success, but will be nonzero if the bundle file is invalid\&. +prints a list of missing commits, if any\&. Finally, information about additional capabilities, such as "object filter", is printed\&. See "Capabilities" in +\fBgitformat-bundle\fR(5) +for more information\&. The exit code is zero for success, but will be nonzero if the bundle file is invalid\&. .RE .PP list\-heads <file> @@ -386,18 +388,9 @@ $ git ls\-remote mybundle .RE .\} .sp +.SH "FILE FORMAT" +.sp +See \fBgitformat-bundle\fR(5)\&. .SH "GIT" .sp Part of the \fBgit\fR(1) suite -.SH "NOTES" -.IP " 1." 4 -the \fBbundle-format\fR -documentation -.RS 4 -\%git-htmldocs/technical/bundle-format.html -.RE -.IP " 2." 4 -the pack format documentation -.RS 4 -\%git-htmldocs/technical/pack-format.html -.RE |