On Wed, Jul 24, 2013 at 8:38 AM, Edward Berner <e...@bernerfam.com> wrote:
> Specifically, a repository's local state is not cloned (see 2nd paragraph > of section 1.0 of http://www.fossil-scm.org/** > index.html/doc/trunk/www/sync.**wiki<http://www.fossil-scm.org/index.html/doc/trunk/www/sync.wiki>). > Most of the local state can be cloned with other commands but you need > to go a bit out of your way (and have extra permissions?) to do it. > Basically only security-relevant info is not cloned (e.g. user list). Anything which is "content" is cloned. AFAIK shunned artifacts are skipped, but i've never used shunning and could be very wrong. It seems fair for those servers of a project which do house the full > repository to be referred to as the central servers or central repositories. But that's a convention between us mortals, and not one fossil knows about. It remembers which repo it cloned from, but it doesn't give that repo any real special status. If it did, and the Central one burned down in a fire then fossil would be confused, perhaps even lonely. If there were some "this repo is the central copy" flag (for us humans) then another copy of the repo would need to set that flag to take over the responsibility. But what, then, if 2 or 3 people each set that flag? The nature of distributed systems makes (by design) any attempt at building a central authority very difficult or impossible. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
