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.) -- ----- 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
