Bug#474742: debbugs: cannot clone merged bug
On Mon, Apr 07, 2008 at 02:51:37PM -0700, Don Armstrong wrote:
> On Mon, 07 Apr 2008, Marcus Better wrote:
> > Bug is marked as being merged with others. Use an existing clone.
> > I'm not really interested in reassigning any one of the original
> > merged bugs. They are for the original package and the
> > reporter/maintainer probably likes them to remain where they are.
> You still have to pick one of them; whether you unmerge one and
> reassign or unmerge one, clone it, and remerge is up to you.
> > Also the wording "Use an existing clone" doesn't make much sense
> > since the original bugs weren't cloned, but rather merged.
> If they're merged, they're the same bug, and therefore clones of
Clone copies the bug history, and thus it's useful to pick a particular
one of the merged bugs. I think having to unmerge/remerge is a right
pain and there isn't really a good non-implementation reason for it.
Merged bugs aren't clones of each other, because clones have divergent
state whereas merged bugs have synchronised state.
Colin Watson [email@example.com]