On Mar 19, 2009, at 7:31 AM, Hugo Schmitt wrote:

> Hello,
>
> Do I ever need to (or "when should I") "fossil close" ?
> Is the myrepo.fossil file updated when I `close' (I mean, should I  
> close before cloning or something?)


Nothing in the "myrepo.fossil" file changes when you "close".  Close  
just deletes the local _FOSSIL_ file that contains your local check- 
out information.  You can do the same with an "rm" command:  "rm  
_FOSSIL_".  The only difference is that the "close" command warns you  
if you have unsaved changes in your local check-out.

A single repository can support multiple local check-outs.  Each local  
check-out knows about the location of its repository.  But the  
repository knows nothing of the local checkouts.  So you can freely  
move or delete local check-outs without hurting anything.  But the  
repository needs to remain in the same place and with the same name or  
else the local check-outs will stop working since they will be unable  
to find the repository.

It has been suggested that the ability to support multiple local  
checkouts from the same repository is a design flaw in fossil.  Hg, it  
seems, supports exactly one local checkout per repository and in fact  
the repository and the local checkout are the same thing.  If you want  
multiple check-outs, you clone the repository.  Some feel that the  
distinction between local checkout and repository is an unnecessary  
complication.  I'm not so sure, though.  What would you users think if  
we modified fossil so that the repository and the local check-out  
became the same thing and so that there could only be a single local  
check-out per repository and the local checkout would always have the  
repository database at its root?  That could be done in such a way  
that it would be compatible with historical repositories, if it is  
seen as desirable.  The advantage is that the whole issue of "open"  
and "close" go away with an accompanying reduction in complexity of  
operation.  The disadvantage is reduced flexibility.


D. Richard Hipp
d...@hwaci.com



_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to