Update working tree parents when pulling new ancestry

Bug #55845 reported by Robert Collins
2
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned
Breezy
Triaged
Low
Unassigned

Bug Description

If I have a working tree at revision C, with a pending merge of B and do a pull from a branch which brings in revision A, which has C in its ancestry, and B in its ancestry, we currently leave B as a pending merge - but this is in fact incorrect - we've pulled in the merge of B already.

I think the right thing to do on pull is to remove all parents of the tree which are now in the ancestry of the new left most parent.

Tags: workingtree
Revision history for this message
Vincent Ladeuil (vila) wrote : Re: Update ancestry of working tree with pending merges

I updated the description summary as empty summaries made the bug unclickable in lists. Please check.

description: updated
Revision history for this message
John A Meinel (jameinel) wrote : Re: Update working tree pending merges when pulling new ancestry

Fixing the title to be even more accurate. Marking it as a real bug with medium priority. It probably doesn't happen often, but our current code would generate semi-incorrect ancestry information.

description: updated
Changed in bzr:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Jelmer Vernooij (jelmer)
tags: added: workingtree
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
tags: removed: check-for-breezy
Changed in brz:
status: New → Incomplete
status: Incomplete → Triaged
importance: Undecided → Low
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.