As well as checking for the presence of tags it should also check that the revisions referred to are in the ancestry of the branch

Bug #264701 reported by James Westby
2
Affects Status Importance Assigned to Milestone
bzr-builddeb
Fix Released
Medium
Unassigned

Bug Description

When "uncommit" is done then tags that refer to those revisions that are removed
from the branch are not removed, so just looking up a tag doesn't mean that it should
be used. It should be checked that the revision is present in the ancestry of the branch
as well.

If a tag is found, but is not present in the ancestry it should be ok to just move it.

E.g. "merge-upstream; uncommit; merge-upstream" will currently not be allowed,
as the tag set by the first is still present.

Related branches

James Westby (james-w)
description: updated
Changed in bzr-builddeb:
importance: Undecided → Medium
status: New → Confirmed
James Westby (james-w)
Changed in bzr-builddeb:
milestone: none → 2.0.1
James Westby (james-w)
Changed in bzr-builddeb:
status: Confirmed → Fix Committed
James Westby (james-w)
Changed in bzr-builddeb:
status: Fix Committed → Fix Released
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.