On Wed, 13 Jul 2011 19:30:08 -0400
Joshua Paine <jos...@letterblock.com> wrote:
> 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.
So do I. This means fossil can do something that you can't do with git
or hg (and probably other DSCMs) that CSCMs do: have multiple working
copies open from the same repo. I use this to keep different working
copies open to different branches, so I can move code between branches
just by merging. If I were using a hg or git, I'd have to push/pull
the changes between the repos in each working copy before I could
merge them.
<mike
--
Mike Meyer <m...@mired.org> http://www.mired.org/
Independent Software developer/SCM consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
