combine-thread silently drops unmerged changes

Bug #200819 reported by Forest Bond
4
Affects Status Importance Assigned to Milestone
Loom
Confirmed
High
Unassigned

Bug Description

combine-thread happily kills a thread still containing unmerged changes, and doesn't warn the user that this is happening.

Requiring --force would be good.

Revision history for this message
Dan Watkins (oddbloke) wrote :
Changed in bzr-loom:
importance: Undecided → High
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.