On Thu, Apr 2, 2015 at 12:20 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Duy Nguyen <pclouds@xxxxxxxxx> writes: > >> Alternatively, we can record SHA-1 in the shallow file as refs whose >> name is always ".shallow". This way "unbundle" can recreate the >> shallow file if it wants. > > Wouldn't the extracting end care about such a name ".shallow" being > duplicates (if you have multiple boundaries) or not check-ref-format > kosher? I think we are careful to ignore funny ref names, so it should not be a problem. But I haven't tested this. > I was hoping we will have a solution for a new bundle command to > create a bundle out of a shallow repository that is somehow usable > by existing 'git bundle' implementations. You may take a bundle out > of a shallow repository to preserve your work on top since you made > the shallow clone originally, and then send it to your friend with > existing 'git bundle' implementation to extract it into his full > clone to sneaker-net. OK two additional options on top of what we already have: - save .have and add extra prerequisite SHA-1. - create a bundle that does not hit shallow boundary in the first place, roughly speaking it's "max depth minus one". This one does not have extra .have or prerequisites -- Duy -- 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