Re: warning: no common commits - slow pull

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

Thanks,
jdl
--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux