From: Junio C Hamano <gitster@pobox.com>
To: jidanni@jidanni.org
Cc: mdl123@verizon.net, gitster@pobox.com, spearce@spearce.org,
git@vger.kernel.org
Subject: Re: [PATCH] git-bundle(1): add no references required simplest case
Date: Mon, 26 Jan 2009 11:53:21 -0800 [thread overview]
Message-ID: <7vljsx6dzi.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <87d4e97uxb.fsf_-_@jidanni.org> (jidanni@jidanni.org's message of "Tue, 27 Jan 2009 03:02:08 +0800")
jidanni@jidanni.org writes:
> Signed-off-by: jidanni <jidanni@jidanni.org>
> ---
> See http://article.gmane.org/gmane.comp.version-control.git/103576
> Documentation/git-bundle.txt | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt
> index 1b66ab7..7c1e990 100644
> --- a/Documentation/git-bundle.txt
> +++ b/Documentation/git-bundle.txt
> @@ -164,6 +164,13 @@ $ git pull bundle
> would treat it as if it is talking with a remote side over the
> network.
>
> +If a bundle requires no references, one may simply use:
Two nits.
1. Bundle does not require reference;it requires commits.
2. "One may simply use:" with a recipe without saying what the recipe is
useful for is not very helpful.
The second point needs to be stressed. For example, you could say
something like this:
With any bundle, you may simply say:
$ git ls-remote bundle.bdl
and it is a correct description if it is to see the refs in the bundle is
what you want to do, but it does not help when cloning from it is what you
want.
It would be a good practice to make the new part go with the flow of the
existing examples. Adding the following at the end might be a better way
to do this than your "init then pull" example:
A complete bundle is one that does not require you to have any
prerequiste 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 is 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.
next prev parent reply other threads:[~2009-01-26 19:54 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 [this message]
2009-01-29 15:32 ` [PATCH,v2] " jidanni
2009-02-01 23:42 ` jidanni
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=7vljsx6dzi.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.org \
--cc=mdl123@verizon.net \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).