From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Mar 2016, #04; Wed, 23)
Date: Thu, 24 Mar 2016 14:51:02 -0700 [thread overview]
Message-ID: <xmqqfuvf7dfd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <171B6E119FCF4E5CBF2831F6A7A004EA@PhilipOakley> (Philip Oakley's message of "Thu, 24 Mar 2016 21:47:20 -0000")
"Philip Oakley" <philipoakley@iee.org> writes:
> This was just clarifying that if a variant of the bundle format (#
> V3?) was used, that it must, if the name was retained(*), still work
> as a sneakernet transfer option. In that case the user would need to
> be told, or be able to find out via (e.g.) the 'verify' sub-command,
> where the other half of the split bundle (the pack) was located so
> that both halves could be copied for sneakernet transfer.
I was sort-of expecting that users are intelligent enough to not
even imagine to use split-bundle for sneakernetting, as it would be
obvious that there is no upside for doing so.
prev parent reply other threads:[~2016-03-24 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 21:12 What's cooking in git.git (Mar 2016, #04; Wed, 23) Junio C Hamano
2016-03-24 7:42 ` Philip Oakley
2016-03-24 16:14 ` Junio C Hamano
2016-03-24 21:47 ` Philip Oakley
2016-03-24 21:51 ` Junio C Hamano [this message]
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=xmqqfuvf7dfd.fsf@gitster.mtv.corp.google.com \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.