After running update dialog the working tree does not get refreshed.

Bug #529891 reported by Craig Hewetson on 2010-03-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Explorer

Bug Description

NOTE this happens when the update causes a conflict. The process results in an "error" and therefore the refreshing mechanism doesn't kick in.

I would expect it to refresh so that the user can see the working tree with the newly created conflicts.

Ian Clatworthy (ian-clatworthy) wrote :

Agreed. I'm also seeing the same problem when Merge has conflicts.

Changed in bzr-explorer:
importance: Undecided → High
status: New → Confirmed
Alexander Belchenko (bialix) wrote :

That's reasonable.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers