On 12/19/12 22:57, Remigiusz Modrzejewski wrote: >>> It stands in stark contrast to Fossil's "everybody has a copy of >>> everything". >> >> Except for private branches. There's been some discussion about adding >> more control over push/pull to fossil, but I don't believe it's >> happened yet. > > Private branches are a pretty recent addition. I believe that the fine > grained pushing/pulling will also come sooner or later, once one of folks > involved with Fossil feels a need for it.
Oh, there's definitely a need for it. Like I have mentioned several times before; the full NetBSD fossil repository is unusable for regular source management work. If one could check out individual branches, then perhaps it would become usable (though that's pure speculation at this point). A while back I did some preliminary work to see how one would implement branch-specific pulls, but before moving along with it I (obviously) asked on the mailing-list to see if anyone else was working on it. And at the time, someone was. And last I heard, there had been some significant progress done, but with a few issues to be resolved. Unfortunately, I haven't seen anything on this for quite a while now, so I get a feeling it was abandoned. And currently I don't have the time to pick it up myself. ..the proper solution would be to look into the scalability issues without looking into limited clones -- but there's also a point in limiting the size of the transfer, so the limited clone feels like a better "first try" project, since it *definitely* solves one issue, and _may_ solve another one. -- Kind regards, Jan Danielsson _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
