[rfc] remove foo.bar; add foo.bar -> make this no-op?

[Alexander Belchenko]

If I have some tree and during my work accidentally remove some 
versioned file by

$ bzr remove foo.bar

Then it becomes unversioned. There is no way (only revert) to undo this.
Sometimes it's enough, but sometimes not. E.g. when I do manual 
resolving of merge conflicts I simply don't want to undo all work.
If I do 'bzr add' before 'bzr commit' file becomes versioned again but 
with another file-id. So bzr treats it as fresh new file.

Is there is a way to tell bzr that this added file is old file, i.e. use 
old file-id and don't break file history?

I mean that between commits pairs of

$ bzr remove foo.bar
$ bzr add foo.bar

Could work as no-op.

?

--
Alexander