0.18: checking removes files automatically?

[Jari Aalto]

* Thu 2007-08-16 Aaron Bentley <aaron.bentley AT utoronto.ca>
* Message-Id: 46C456FC.8040509 AT utoronto.ca
>
>> I would not expect that to happen. Only if I flag file
>> specifically as deleted:
>> 
>>     $ bzr rm install.sh
>> 
>> then it would be okay for checkin to remove it.
>> 
>>     $ bzr ci ...
>> 
>
> If you use commit --strict, then it will notice that install.sh.tmp is
> not versioned and not ignored, and abort the commit.

But I have many temporary files that are not versioned, so --strict
would not probably work?

> There's been some discussion of adding the behavior you were expecting,
> and that's fine with me, as long as I can still have the current default
> behavior.

I think the current behavior is dangerous. In CVS, you could always
accidentally do:

    rm *            ;;  Oops, should have been "rm .*"

Now problem. You restore the previous condition with:

    cvs up

Not so with bzr.

Bzr assumes too much for a missing file (upon ci). The current
behavior does not preserve data, but causes headaches on accidents.
Is there a plan when this will be taken into roadmap?

Jari