On 7/13/2011 7:13 PM, Brian Cottingham wrote: > was wondering if some of the Fossil internals > could be refactored to not need an explicit 'open' command. I.E., Git > and SVN don't need an open command- you just cd into a repo's directory > and stuff works. Could Fossil be reworked to act similarly?
Ok, now I see. In git the repo is a hidden directory containing many files stored in the same directory as the 'working copy' (to use a SVN term). The fossil repo, however, is a single SQLite database file with a special schema. So there is no repo directory to CD into until you open a repo in a directory. Once you've done that (one-time operation), all the commands do work in that dir without further fanfare. I don't see this changing anytime soon, as drh (I believe) regards this as a feature. I agree, fwiw. Besides the coolness of a very portable and backup-able repo file and among other things, it makes it really trivial to have different branches of the same repo open at the same time in different directories without recourse to an outside server (or indeed any server). I expect that's possible in git, too, but of all the git users I know personally, I'm pretty sure none of them know how. (I don't.) -- Joshua Paine LetterBlock: Web Applications Built With Joy http://letterblock.com/ 301-576-1920 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
