rm with bzr

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Erik Bågfors wrote:
> On 11/20/06, Alex Chen <alex.chenhl at gmail.com> wrote:
>> Thank you very much for your helpful answer!
>>
>> Could you show me the link to the debate? I'd like to know what's
>> advantage
>> and senario of this intentioned behavior.
> 
> I have seen no such thing.

I thought there was actually an open bug on this, but I don't seem to be
able to find it right now.  But basically, we did decide that we want to
'fail' a commit if there are missing files, rather than marking them as
removed. We should have a 'commit --auto' which does that sort of thing,
but only on request.

Especially since 'mv a b; bzr commit' will remove a, since you forgot to
tell bzr that a actually moved, and wasn't deleted.

> 
>> And actually I still wonder about the following question, could you
>> help me
>> out?
>> When I try "bzr log foo.c", bzr will show all the related rev that
>> changes
>> the file. While "bzr log ." only showed the "initial" revision,
>> although I
>> had check-in for adding or removing files for several
>> times under this directory. Is the files adding and removing a kind of
>> change for directory? If it is, why not log report the related revisions?
> 
> I can't reproduce this.
> Can you tell me what you are doing to get this?
> 
> /Erik

I think he is saying that if you log changes to a 'directory', he wants
it to be the changes to the files (possibly recursive).

At the moment, 'bzr log dir' only shows changes to the directory itself
(rename, add, move, etc).

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFYc4UJdeBCYSNAAMRAt+3AKDAeqBAAnRnGubyNfAgsjHmMgW8gACfe0hp
gRAV9lR7mPaSto+B4FrKADQ=
=55oC
-----END PGP SIGNATURE-----