From: jidanni@jidanni•org
To: gitster@pobox•com
Cc: mdl123@verizon•net, spearce@spearce•org, git@vger•kernel.org
Subject: Re: [PATCH,v2] git-bundle(1): add no references required simplest case
Date: Mon, 02 Feb 2009 07:42:51 +0800 [thread overview]
Message-ID: <87pri12078.fsf@jidanni.org> (raw)
In-Reply-To: 87tz7i6scg.fsf_-_@jidanni.org
Words totally by Junio C Hamano.
Signed-off-by: jidanni <jidanni@jidanni•org>
---
Junio: I used your words.
You might have missed this patch. Resending.
Documentation/git-bundle.txt | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt
index 1b66ab7..42c2abc 100644
--- a/Documentation/git-bundle.txt
+++ b/Documentation/git-bundle.txt
@@ -164,6 +164,22 @@ $ git pull bundle
would treat it as if it is talking with a remote side over the
network.
+A complete bundle is one that does not require you to have any
+prerequisite object for you to extract its contents. Not only you
+can fetch/pull from a bundle, you can clone from a complete bundle
+as if it was a remote repository, like this:
+
+----------------
+$ git clone /home/me/tmp/file.bdl mine.git
+----------------
+
+This will define a remote called "origin" in the resulting
+repository that lets you fetch and pull from the bundle, just
+like the previous example lets you do with the remote called
+"bundle", and from then on you can fetch/pull to update the
+resulting mine.git repository after replacing the bundle you store
+at /home/me/tmp/file.bdl with incremental updates.
+
Author
------
Written by Mark Levedahl <mdl123@verizon•net>
--
1.6.0.6
next prev parent reply other threads:[~2009-02-01 23:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 19:29 How to extract files out of a "git bundle", no matter what? jidanni
2008-12-19 19:32 ` Shawn O. Pearce
2008-12-19 19:57 ` Mark Levedahl
2008-12-19 20:13 ` jidanni
2008-12-19 20:21 ` Jeff King
2008-12-19 20:35 ` jidanni
2008-12-19 20:51 ` Jeff King
2009-01-01 4:24 ` [PATCH] Documentation/git-bundle.txt: Dumping contents of any bundle jidanni
2009-01-01 17:03 ` Johannes Schindelin
2009-01-01 19:21 ` Jeff King
2009-01-01 22:12 ` jidanni
2009-01-01 23:48 ` Jeff King
2009-01-02 0:10 ` jidanni
2009-01-02 7:15 ` Shawn O. Pearce
2009-01-02 8:27 ` Jeff King
2009-01-02 22:03 ` jidanni
2009-01-01 23:18 ` git ls-tree prints wacko file sizes if it can't find the blob jidanni
2009-01-01 23:47 ` jidanni
2009-01-01 23:52 ` [PATCH] Handle sha1_object_info failures in ls-tree -l Alex Riesen
2009-01-26 19:02 ` [PATCH] git-bundle(1): add no references required simplest case jidanni
2009-01-26 19:53 ` Junio C Hamano
2009-01-29 15:32 ` [PATCH,v2] " jidanni
2009-02-01 23:42 ` jidanni [this message]
2009-02-02 0:04 ` Johannes Schindelin
2009-02-02 0:45 ` Junio C Hamano
2009-02-04 0:09 ` jidanni
2009-02-04 2:07 ` Junio C Hamano
2009-02-04 2:18 ` jidanni
2009-02-04 9:15 ` [PATCH] git-bundle doc: update examples Nanako Shiraishi
2009-02-04 15:26 ` Jeff King
2009-02-04 22:44 ` Junio C Hamano
2008-12-19 20:07 ` How to extract files out of a "git bundle", no matter what? Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pri12078.fsf@jidanni.org \
--to=jidanni@jidanni$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=mdl123@verizon$(echo .)net \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox