On Fri, 29 Feb 2008, Jon Loeliger wrote: > Shawn O. Pearce wrote: > > "Shawn O. Pearce" <spearce@xxxxxxxxxxx> wrote: > > > Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote: > > > > I agree its outside of 1.5.5, as we'd all like to see 1.5.5 happen > > > soon, but it could be 1.5.6 material, especially if someone starts > > > working on it sooner rather than later. > > > > > > Its actually probably not that difficult to implement. > > > > OK, so I posted a fairly short series tonight (4 patches) that > > handles some of the common cases in a fairly small amount of > > code churn. It might just be 1.5.5-ish. > > > > Doing anything better is going to require a new protocol extension, > > which is already 1.5.6 material. In the mean time maybe Junio's > > earlier patch to try and drop the ref_map when we do open the new > > connection is the way to deal with the round-robin DNS issues. > > > Hmmm... Might the any protocol extensions require a 1.6 release > rather than a 1.5.x release? Or is this extension compatible > enough that it can be transparent? The client and server exchange a list of supported features at the beginning, and the difference in behavior would be at the end, so it should be no problem to have the client ask for the chance to make further requests and the server acknowledge that (or the server offer and the client accept, depending on the order they do it, which I don't remember) without affecting programs that don't report the feature. -Daniel *This .sig left intentionally blank* -- 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
