For some irrational reason I avoid addremove as well. I find myself piping
fossil changes through grep and awk and then xargs-ing back to fossil rm or
add whenever it comes up - and I *know* that addremove will do the same
thing.
I just can't bring myself to use it :)
On Monday, September 2, 2013, Stephan Beal wrote:
> On Mon, Sep 2, 2013 at 8:41 PM, Martin S. Weber
> <ephae...@gmx.net<javascript:_e({}, 'cvml', '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?
>
> 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.
>
> --
> ----- 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
