On Mon, Sep 02, 2013 at 07:54:35PM +0200, Stephan Beal wrote: > On Mon, Sep 2, 2013 at 8:41 PM, Martin S. Weber <ephae...@gmx.net> wrote: > > > I find it easy to bring my checkout to the state I want the DB to reflect > > and then just go ahead and do so in a single swoop. "Getting (all) files > > in place and teaching fossil about it" is one of my "use case"s, if you > > will. > > > > i can see that being useful for an initial setup, but how often do you set > up new repos? Surely you do other things more often than addremove?
For me, new functionality often includes adding one or two source files, a test file, mock data, templates and other data that is being used by the functionality, etc. I blitz in a couple new files every now and then, or get rid of a bunch, and then sync fossil with my checkout. Of course I'm not doing it that often, one of my current projects, a month's worth of development, has seen about a dozen instances of addremove after the initial setup. > What i tend to do with a new tree is kind of sloppy: > > f add . > fst > > and then go 'f rm' any which i don't want. I tend not to have files in my checkout that don't belong into fossil. If files are not there, and fossil thinks they are, they need deleting from fossil very often. Usually comes in conjunction to adding a bunch of other files :) Anyways, that's how I use it. Regards, -Martin _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
