Comment 41 for bug 45719

I remember from my CVS days that this used to happen, but can't come up with a clear example now. It was probably because I version control the logfile output of some of my testcases, to have a "golden" version. If I introduced a bug, I would catch the problem when comparing the committed, golden logfile to the newly generated one. Then, I would try and roll back the source code (sometimes a subset of it) and re-run the testcase until the test output compared favourably with the golden version. Hopefully that makes sense -- it's been a while.

Even without uncommitted changes, it should be possible to get a clean checkout of some previous revision into one's working directory, and with "bzr status -V" reporting in a very satisfying way that you haven't edited anything. Otherwise I cannot distinguish my recent edits from changes due to the rollback. Therefore, I'm looking forward to trying bzr update!

By the way, will "bzr update -r" work on specific files or directories, or will the rollback necessarily be applied to the entire tree? I noticed that there is a "DIR" argument to update in the 2.1 user reference manual. If there is granularity, I guess this begs the question as to what the revno is. It would be nice to be able to roll back a specific module instead of the whole project.

I've really had no luck installing the release candidate. Is there an Ubuntu package available?

Thx

Julien