Documentation should clarify that revert only changes files, not last-revision

using the dapper package, version 0.7-2 .

On Tue, Mar 07, 2006 at 11:19:22AM -0000, Sivan Greenberg wrote:
> Public bug reported:
> https://launchpad.net/malone/bugs/33973
>
> Affects: bzr (upstream)
> Severity: Normal
> Priority: (none set)
> Status: Unconfirmed
>
> Description:
> sivan@ubuntu:~/my/upb-coroutines-pexpect_with_pre-build_function/utils-and-GUI$ bzr revno
> 184
> sivan@ubuntu:~/my/upb-coroutines-pexpect_with_pre-build_function/utils-and-GUI$ bzr revert -r 173
> sivan@ubuntu:~/my/upb-coroutines-pexpect_with_pre-build_function/utils-and-GUI$ bzr revno
> 184
>
>
> Now, as the revision is really 173 (by checking the source files) bzr reports 183 (the latest).
>
> Rather confusing and makes you think bzr is doing something wrong.

As Robert said on irc, revert only changes the working tree contents.
Showing the revno that is at if it differs from the branch seems to me
like a good improvement.

Wouter van Heyst

this is a documentation and UI issue: revert is behaving as desired, but we should make it more clear to users what it is that its going to do. If users want to switch to an older revno in a tree, they should consider using either 'update -r revno' [possibly not supported yet], or uncommit [if that matches their intent]. We shoud guide them towards these actions.