Re: warning: no common commits - slow pull
- From
Jon Loeliger <jdl@freescale.com>
- Date
- Feb 29, 2008, 14:44 UTC
- Message-ID
- <47C81A6B.1060905@freescale.com>
- In-Reply-To
- <20080228085038.GS8410@spearce.org>
Shawn O. Pearce wrote:
> "Shawn O. Pearce" <spearce@spearce.org> wrote: >> Daniel Barkalow <barkalow@iabervon.org> wrote:
Show 14 quoted lines
>> 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?
Thanks, jdl