{"thread":{"id":"32496","subject":"[PATCH] Correct example restore from bundle","startedAt":"2013-01-01T15:26:13Z","lastAt":"2013-01-01T21:08:47Z","messageCount":4,"participants":["Kirill Brilliantov","Junio C Hamano","W. Trevor King"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"205768","messageId":"1357053973.22772208@f75.mail.ru","threadId":"32496","inReplyTo":null,"subject":"[PATCH] Correct example restore from bundle","fromName":"Kirill Brilliantov","fromEmail":"brilliantov@inbox.ru","sentAt":"2013-01-01T15:26:13Z","receivedAt":"2013-01-01T15:26:13Z","isPatch":true,"sender":{"key":"brilliantov@inbox.ru","avatar":null},"body":"Without use branche option repository restory without files:\n$ git clone pr.bundle q/\nCloning into 'q'...\nReceiving objects: 100% (619/619), 13.52 MiB | 18.74 MiB/s, done.\nResolving deltas: 100% (413/413), done.\nwarning: remote HEAD refers to nonexistent ref, unable to checkout.\n$ ls -aF q/\n./  ../  .git/\n\nSigned-off-by: Brilliantov Kirill Vladimirovich <brilliantov@inbox.ru>\n---\n Documentation/git-bundle.txt |    2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt\nindex 16a6b0a..6c31715 100644\n--- a/Documentation/git-bundle.txt\n+++ b/Documentation/git-bundle.txt\n@@ -118,7 +118,7 @@ were a remote repository instead of creating an empty repository and then\n pulling or fetching objects from the bundle:\n \n ----------------\n-machineB$ git clone /home/me/tmp/file.bundle R2\n+machineB$ git clone /home/me/tmp/file.bundle R2 -b master\n ----------------\n \n This will define a remote called \"origin\" in the resulting repository that\n-- \n1.7.10.4"},{"id":"205779","messageId":"7vvcbgaapq.fsf@alter.siamese.dyndns.org","threadId":"32496","inReplyTo":"1357053973.22772208@f75.mail.ru","subject":"Re: [PATCH] Correct example restore from bundle","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-01-01T20:51:13Z","receivedAt":"2013-01-01T20:51:13Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Kirill Brilliantov <brilliantov@inbox.ru> writes:\n\n>  ----------------\n> -machineB$ git clone /home/me/tmp/file.bundle R2\n> +machineB$ git clone /home/me/tmp/file.bundle R2 -b master\n\nI think the command line should follow the convention that is\nsuggested in \"git clone -h\" output, i.e.\n\n    git clone -b master /home/me/tmp/file.bundle R2\n\nI also think 'git bundle create\" should record HEAD that points at\nthe only branch it is packing so the person who clones from it\nshould not say which branch, and when that is done this patch will\nbecome unnecessary, but that is a separate topic.\n\nThanks; I'll queue this after rewording some.\n\n-- >8 --\nFrom: Kirill Brilliantov <brilliantov@inbox.ru>\nDate: Tue, 1 Jan 2013 17:54:44 +0400\nSubject: [PATCH] Documentation: correct example restore from bundle\n\nBecause the bundle created in the example does not record HEAD, \"git\nclone\" will not check out the files to the working tree:\n\n    $ git clone pr.bundle q/\n    Cloning into 'q'...\n    Receiving objects: 100% (619/619), 13.52 MiB | 18.74 MiB/s, done.\n    Resolving deltas: 100% (413/413), done.\n    warning: remote HEAD refers to nonexistent ref, unable to checkout.\n\nAvoid alarming the readers by adding \"-b master\" to the example.  A\nbetter fix may be to arrange the bundle created in the earlier step\nto record HEAD, so that it can be cloned without this workaround.\n\nSigned-off-by: Brilliantov Kirill Vladimirovich <brilliantov@inbox.ru>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>\n---\n Documentation/git-bundle.txt | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt\nindex 16a6b0a..5c8ba44 100644\n--- a/Documentation/git-bundle.txt\n+++ b/Documentation/git-bundle.txt\n@@ -118,7 +118,7 @@ were a remote repository instead of creating an empty repository and then\n pulling or fetching objects from the bundle:\n \n ----------------\n-machineB$ git clone /home/me/tmp/file.bundle R2\n+machineB$ git clone -b master /home/me/tmp/file.bundle R2\n ----------------\n \n This will define a remote called \"origin\" in the resulting repository that\n-- \n1.8.1.209.gc32ab23\n"},{"id":"205782","messageId":"7vehi4a9za.fsf_-_@alter.siamese.dyndns.org","threadId":"32496","inReplyTo":"7vvcbgaapq.fsf@alter.siamese.dyndns.org","subject":"[PATCH] Documentation: full-ness of a bundle is significant for cloning","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-01-01T21:07:05Z","receivedAt":"2013-01-01T21:07:05Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Not necessarily every bundle file can be cloned from.  Only the ones\nthat do not need prerequisites can.\n\nWhen 1d52b02 (Documentation: minor grammatical fixes and rewording\nin git-bundle.txt, 2009-03-22) reworded this paragraph, it lost a\ncritical hint to tell readers why thhis particular bundle can be\ncloned from.  Resurrect it.\n\nSigned-off-by: Junio C Hamano <gitster@pobox.com>\n---\n\n * As I noticed this while I was looking at Kirill's patch...\n\n Documentation/git-bundle.txt | 7 +++----\n 1 file changed, 3 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt\nindex 5c8ba44..bc023cc 100644\n--- a/Documentation/git-bundle.txt\n+++ b/Documentation/git-bundle.txt\n@@ -112,10 +112,9 @@ machineA$ git bundle create file.bundle master\n machineA$ git tag -f lastR2bundle master\n ----------------\n \n-Then you transfer file.bundle to the target machine B. If you are creating\n-the repository on machine B, then you can clone from the bundle as if it\n-were a remote repository instead of creating an empty repository and then\n-pulling or fetching objects from the bundle:\n+Then you transfer file.bundle to the target machine B. Because this\n+bundle does not require any existing object to be extracted, you can\n+create a new repository on machine B by cloning from it:\n \n ----------------\n machineB$ git clone -b master /home/me/tmp/file.bundle R2\n-- \n1.8.1.209.gc32ab23\n"},{"id":"205799","messageId":"20130101210847.GB5362@odin.tremily.us","threadId":"32496","inReplyTo":"7vehi4a9za.fsf_-_@alter.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: full-ness of a bundle is significant for cloning","fromName":"W. Trevor King","fromEmail":"wking@tremily.us","sentAt":"2013-01-01T21:08:47Z","receivedAt":"2013-01-01T21:08:47Z","isPatch":true,"sender":{"key":"wking@tremily.us","avatar":"https://avatars.githubusercontent.com/u/209920?v=4"},"body":"On Tue, Jan 01, 2013 at 01:07:05PM -0800, Junio C Hamano wrote:\n> critical hint to tell readers why thhis particular bundle can be\n\ns/thhis/this/\n"}]}