how to revert update operation

[Alexander Belchenko]

Robert Collins пишет:
> On Tue, 2006-07-18 at 15:32 +0300, Alexander Belchenko wrote:
>>Robert Collins пишет:
>>>On Tue, 2006-07-18 at 15:19 +0300, Alexander Belchenko wrote:
>>>>Adeodato Simó пишет:
>>>>>* Alexander Belchenko [Tue, 18 Jul 2006 14:59:18 +0300]:
>>>>>
>>>>>>Is there is any chance to ressurect my --local work? I don't remember
>>>>>>revid, but may be there is hidden command to browse all revisions that
>>>>>>present in repository? Or after update this revisions simply throwed away?
>>>>>
>>>>>If after the update you didn't do anything else, your --local commits
>>>>>will be present as pending merges:
>>>>>
>>>>> % bzr status
>>>>> % bzr commit -m 'Merge --local work'
>>>>
>>>>Oops. My fingers moves faster than I think. I also run revert. :-(
>>>>And after revert I lose all.
>>>
>>>
>>>We should make update tell you clearly that your work is now ready to
>>>commit to the mainline, so that its more clear.
>>
>>When I run 'bzr info' it also don't print me anything about divergence 
>>between local and master branch.
> 
> Ah, because there is none - all the work is now pending merge - pending
> a commit.
> 
> I dont know, but info should show that too IMO.

I mean that when local and master branch is diverged and local branch
have extra revisions in compare with master branch, there is no mention
in output of bzr info.

And after 'bzr update' I see this report:

$ bzr update
All changes applied successfully.
All changes applied successfully.
Updated to revision 107.

Why it prints twice?

--
Alexander