From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: gitList <git@vger.kernel.org>
Subject: Re: [PATCHv2 1/8] Doc: Bundle file usage
Date: Tue, 18 Sep 2012 16:55:11 -0700 [thread overview]
Message-ID: <7vzk4mj38g.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1348010734-664-2-git-send-email-philipoakley@iee.org> (Philip Oakley's message of "Wed, 19 Sep 2012 00:25:27 +0100")
Philip Oakley <philipoakley@iee.org> writes:
> Git URLs can accept bundle files for fetch, pull and clone, include
> in that section. Include git clone in the bundle usage description.
> Correct the quoting of <git-rev-list-args>.
> Detail the <git-rev-list-args> '--all' option for cloning.
>
> Signed-off-by: Philip Oakley <philipoakley@iee.org>
>
> diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt
> index 16a6b0a..be6a5f1 100644
> --- a/Documentation/git-bundle.txt
> +++ b/Documentation/git-bundle.txt
> @@ -21,12 +21,12 @@ Some workflows require that one or more branches of development on one
> machine be replicated on another machine, but the two machines cannot
> be directly connected, and therefore the interactive git protocols (git,
> ssh, rsync, http) cannot be used. This command provides support for
> -'git fetch' and 'git pull' to operate by packaging objects and references
> -in an archive at the originating machine, then importing those into
> -another repository using 'git fetch' and 'git pull'
> -after moving the archive by some means (e.g., by sneakernet). As no
> -direct connection between the repositories exists, the user must specify a
> -basis for the bundle that is held by the destination repository: the
> +'git fetch', 'git pull' and 'git clone', to operate by packaging
> +objects and references in an archive at the originating machine, then
> +importing those into another repository using 'git fetch', 'git pull',
> +or 'git clone', after moving the archive by some means (e.g., by sneakernet).
> +As no direct connection between the repositories exists, the user must
> +specify a basis for the bundle that is held by the destination repository: the
> bundle assumes that all objects in the basis are already in the
> destination repository.
>
> @@ -35,7 +35,7 @@ OPTIONS
>
> create <file>::
> Used to create a bundle named 'file'. This requires the
> - 'git-rev-list-args' arguments to define the bundle contents.
> + <git-rev-list-args> arguments to define the bundle contents.
>
> verify <file>::
> Used to check that a bundle file is valid and will apply
> @@ -92,6 +92,8 @@ It is okay to err on the side of caution, causing the bundle file
> to contain objects already in the destination, as these are ignored
> when unpacking at the destination.
>
> +To create a bundle for 'git clone', use `--all` for the <git-rev-list-args>.
> +
Hmm, what does this mean? Specifically, it is not clear what "for
'git clone'" exactly means. It is not "for use of 'git clone'",
because you should be able to create a bundle that has 'master'
branch without 'maint', 'next', and 'pu' and clone from it, no?
git checkout maint
git bundle create /var/tmp/1.bndl HEAD refs/heads/maint
cd /var/tmp && git clone 1.bndl xprm
I also think "--all" is a bad advice for another reason. Doesn't it
shove refs from refs/remotes/* hierarchy in the resulting bundle?
It is fine for archiving purposes, but it does not seem to be a good
advice to create a bundle to clone from.
> EXAMPLE
> -------
>
> diff --git a/Documentation/urls.txt b/Documentation/urls.txt
> index 2890194..2d75cce 100644
> --- a/Documentation/urls.txt
> +++ b/Documentation/urls.txt
> @@ -42,6 +42,9 @@ These two syntaxes are mostly equivalent, except the former implies
> --local option.
> endif::git-clone[]
>
> +'git clone', 'git fetch' and 'git pull', but not 'git push', will also
> +accept a suitable bundle file. See linkgit:git-bundle[1].
> +
> When git doesn't know how to handle a certain transport protocol, it
> attempts to use the 'remote-<transport>' remote helper, if one
> exists. To explicitly request a remote helper, the following syntax
next prev parent reply other threads:[~2012-09-18 23:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 23:25 [PATCHv2 1/8] Doc: Bundle file usage Philip Oakley
2012-09-18 23:55 ` Junio C Hamano [this message]
2019-10-16 9:57 ` [PATCH v2] " Philip Oakley
2019-10-16 10:15 ` Philip Oakley
2019-10-16 21:09 ` Jeff King
2019-10-17 2:54 ` Junio C Hamano
2019-10-18 15:15 ` [PATCH v3] " Philip Oakley
2019-10-18 18:15 ` Pratyush Yadav
2019-10-18 19:58 ` Philip Oakley
2019-10-18 20:30 ` [PATCH v4] " Philip Oakley
2019-10-20 1:10 ` Jeff King
2019-10-20 10:49 ` Philip Oakley
2019-10-20 11:03 ` [PATCH v5] " Philip Oakley
2019-10-21 2:48 ` Junio C Hamano
2019-10-21 3:16 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vzk4mj38g.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).