[PATCH] Documentation: full-ness of a bundle is significant for cloning
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 1, 2013, 21:07 UTC
- Message-ID
- <7vehi4a9za.fsf_-_@alter.siamese.dyndns.org>
- In-Reply-To
- <7vvcbgaapq.fsf@alter.siamese.dyndns.org>
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 thhis particular bundle can be cloned from. Resurrect it.
Signed-off-by: Junio C Hamano <gitster@pobox.com> ---
* As I noticed this while I was looking at Kirill's patch...
Documentation/git-bundle.txt | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt index 5c8ba44..bc023cc 100644 --- a/Documentation/git-bundle.txt +++ b/Documentation/git-bundle.txt @@ -112,10 +112,9 @@ machineA$ git bundle create file.bundle master machineA$ git tag -f lastR2bundle master ---------------- -Then you transfer file.bundle to the target machine B. If you are creating -the repository on machine B, then you can clone from the bundle as if it -were a remote repository instead of creating an empty repository and then -pulling or fetching objects from the bundle: +Then you transfer file.bundle to the target machine B. Because this +bundle does not require any existing object to be extracted, you can +create a new repository on machine B by cloning from it: ---------------- machineB$ git clone -b master /home/me/tmp/file.bundle R2
-- 1.8.1.209.gc32ab23