warning about local changes after bzr update, even if there aren't any after the update

Bug #562079 reported by Robert Collins on 2010-04-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Medium
Robert Collins

Bug Description

 affects bzr
 status confirmed
 importance high

Making high as this is a UI regression. Not all updates leave local
pending commits, so showing a message about them is inappropriate when
there are none.
======
:!bzr update
All changes applied
successfully.
Updated to revision 202 of branch /home/robertc/source/pqm/public
Your local commits will now show as pending merges with 'bzr status',
and can be committed with 'bzr commit'.

:!bzr st

========

Martin Pool (mbp) on 2010-04-14
summary: - incorrect warning after update
+ warning about local changes after bzr update, even if there aren't any
Changed in bzr:
importance: High → Medium
tags: added: easy local-commits ui update
summary: warning about local changes after bzr update, even if there aren't any
+ after the update
Changed in bzr:
assignee: nobody → Robert Collins (lifeless)
Changed in bzr:
assignee: Robert Collins (lifeless) → nobody
John A Meinel (jameinel) wrote :

A branch landed from Robert with this discussed (specifically about the pending-merges). It doesn't look like this bug is talking about anything else, so I'll mark it as fixed.

Changed in bzr:
assignee: nobody → Robert Collins (lifeless)
milestone: none → 2.2.0
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers