Comment 3 for bug 419323

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A Meinel wrote:
> Aaron Bentley wrote:
>> I can quite well imagine that a proposal to merge X into Y could be
>> superseded by a proposal to merge Z into Y, though. And I can see you
>> might want to re-target a proposal to a release branch instead of trunk.
>> What do you think?

> So I won't say that all proposals to release supersede proposals to
> merge to trunk.

That's not something I proposed, and not something I thought you were
proposing. What do you mean?

> I mostly wanted a way to close my proposal in a clean
> way, as I didn't mean to make it.

We are planning to add a "withdraw" action on branch merge proposals so
that their submitter can withdraw them. Would that seem right in this case?

> 1) Being able to retarget it would have been ok, though slightly
> problematic if I've already submitted a new request and just want to
> close the old one out graciously.

I think that's the sort of corner case that's never going to be perfect.
 But you could delete the new one and retarget the old one. Or delete
the old one if it didn't get used.

> 2) Being able to say that someone else's work is better than your own
> would also be useful (independent of my current use case.)

Cool.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqVco0ACgkQ0F+nu1YWqI1tBACeLSofwdHZHdMJcUis2/ZVDZ1o
kgEAn3wtM7VuNnmndU4WZbbNIfOVW8nA
=+T4+
-----END PGP SIGNATURE-----