I was unclear, apparently.
Suppose "fossil rm *.foo" deletes the files from the file system and
from Fossil.
If I then do
rm *.foo
when I meant to do
fossil rm *.foo
I can then do
fossil update
which will give me my *.foo files back. Then, I can do
fossil rm *.foo
Note that I'd expect "fossil rm *.foo" only to remove files from the
file system that it can remove from the repository, i.e., if I had an
extra file, not_added.foo, I'd expect "fossil rm *.foo" to live it
alone.
Will
On Dec 10, 2009, at 3:20 AM, Benjohn Barnes wrote:
>
> On 9 Dec 2009, at 21:21, [email protected]
> wrote:
>
>> Which is exactly why "fossil rm *.foo" should delete *.foo from the
>> file system as well as from the repository. If you forget, and do
>> "rm
>> *.foo", then you can ask fossil to give you the files back, and then
>> do "fossil rm *.foo" so that you don't need to type in all of the
>> names.
>>
>> Will
>
> Although, I think, as you don't have any globbing, when you "ask
> fossil to give you the files back", you do need to type in all the
> names :-) (unless those deletions are the only changes that you've
> made to the working copy).
>
> _______________________________________________
> fossil-users mailing list
> [email protected]
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
------------------------------------------------------------------
will -at- wjduquette.com | Catch our weblog,
http://foothills.wjduquette.com/blog | The View from the Foothills
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
