Skip to content

Commit b5fb477

Browse files
committed
Documentation: full-ness of a bundle is significant for cloning
Not necessarily every bundle file can be cloned from. Only the ones that do not need prerequisites can. When 1d52b02 (Documentation: minor grammatical fixes and rewording in git-bundle.txt, 2009-03-22) reworded this paragraph, it lost a critical hint to tell readers why this particular bundle can be cloned from. Resurrect it. Signed-off-by: Junio C Hamano <[email protected]>
1 parent ded6aa6 commit b5fb477

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

Documentation/git-bundle.txt

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -112,10 +112,9 @@ machineA$ git bundle create file.bundle master
112112
machineA$ git tag -f lastR2bundle master
113113
----------------
114114

115-
Then you transfer file.bundle to the target machine B. If you are creating
116-
the repository on machine B, then you can clone from the bundle as if it
117-
were a remote repository instead of creating an empty repository and then
118-
pulling or fetching objects from the bundle:
115+
Then you transfer file.bundle to the target machine B. Because this
116+
bundle does not require any existing object to be extracted, you can
117+
create a new repository on machine B by cloning from it:
119118

120119
----------------
121120
machineB$ git clone -b master /home/me/tmp/file.bundle R2

0 commit comments

Comments
 (0)