----- Original Message -----
From: "Junio C Hamano" <gitster@xxxxxxxxx>
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'. The ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
Three more minor fix-up topics are to be merged by 2.8 final, but we
are almost there.
You can find the changes described here in the integration branches
of the repositories listed at
http://git-blame.blogspot.com/p/git-public-repositories.html
--------------------------------------------------
...
[Cooking]
* jc/bundle (2016-03-03) 6 commits
- index-pack: --clone-bundle option
- Merge branch 'jc/index-pack' into jc/bundle
- bundle v3: the beginning
- bundle: keep a copy of bundle file name in the in-core bundle header
- bundle: plug resource leak
- bundle doc: 'verify' is not about verifying the bundle
(this branch uses jc/index-pack and jc/maint-index-pack-keep; is tangled
with jc/index-pack-clone-bundle.)
The beginning of "split bundle", which could be one of the
ingredients to allow "git clone" traffic off of the core server
network to CDN.
...
Hi Junio,
I think there may be a concept clash between the ideals of a 'sneakernet
bundle' and the 'resumable clone'.
The bundle capability still needs to work easily in sneakernet mode, and my
reading of the proposed code for V3 (split-bundle) left the impression that
it would be very hard for the user to do the manual transport of the files
and place the split bundle in the right places such that a local clone from
the bundle would still work.
Part of the issue is getting the naming right so so that there is no
confusion between the two opposing capabilities (on-line vs off-line
transfer).
There were a few other lesser point that I'll address when I have the right
moment to reply to their respective messages.
--
Philip
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html