On Sat, Apr 28, 2012 at 07:25, Stephan Beal <sgb...@googlemail.com> wrote: > On Sat, Apr 28, 2012 at 1:03 PM, Leo Razoumov <slonik...@gmail.com> wrote: >> >> (3) Rational for violating long-standing Fossil design principle that >> project repo database does not know its checkouts. > > > This sounds like it might also (minorly?) complicate out-of-fossil > synchronization of repos for some users (e.g. rsync-based), since a checkout > now changes the repo file? > > Regarding the unlimited growth: i've been using fossil since 2007 and have > never had any given repo checked out more than twice locally. Even with 50 > entries, the storage required is minimal. (Nonetheless, i share your > curiosity about why this new feature might be needed at all.) >
I do checkout a repo often and multiple times -- typically, one checkout-per-branch I am working with (for fossil-scm alone I have 5 checkouts). Please, keep in mind that "fossil open" adds a checkout entry while "fossil close" does *NOT* remove it. Basically, a project repo keeps accumulating checkout entries some of which refer to deleted checkouts that no longer exist! It also clutters output of "fossil info" command. And, of course, it breaks rsync. --Leo-- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
