Junio C Hamano <gitster@xxxxxxxxx> wrote: > "Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > >> How will this mesh with 'git clone --mirror'? > > > > Not well. > > But we at least can assume that the server operator is reasonable and > wouldn't go overboard, (ab)using this "abbreviated advertisement" feature > to hide heads and tags from the clients. Yes. My patch is hardcoded to show only heads and tags, and nothing else. But I think we want to make this configurable, and show everything by default, but if there is a configuration entry, show only what the configuration entry patterns suggest to advertise. Thus an admin could hide refs/heads/*, but maybe he wants to, and show only refs/heads/master, refs/heads/maint, refs/heads/next by default. This is actually a rather clear indication to a client that although there may be individual cooking topics scattered through the expanded refs/heads/* space, any reasonable default clone wouldn't take them. > Think about in what situation you would want to do a mirror clone. ... > That means the version of git used to prime, update > and serve the mirror will know the expand extention. Great point Junio. The backwards compatibility may be a non-issue then, especially if this is configurable and we advertise refs/* by default like we do now, and any reasonable admin who does enable the hiding still advertises the core namspaces that really matter to the majority of clients. > I am hoping that we can finish 1.6.5 by mid September (let's tentatively > say we will shoot for 16th). I expect the expand extention to be in > 'next' by that time, cooking for 1.7.0. How does that timetable sound? Oh, if 1.6.5 is mid-September, this is certainly not 1.6.5 material. I'm not in any rush, this should go in when its ready, but 1.7 might be reasonable. -- Shawn. -- 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