Comment 2 for bug 419323

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

Aaron Bentley wrote:
> John A Meinel wrote:
>> Public bug reported:
>
>> My specific case was that I meant to target an MP to a release branch
>> rather than trunk, and ended up with 2 proposals. I'd like a way to
>> cleanly close one of them.
>
> In our current thinking, your proposal to merge into a release branch is
> a different thing from your proposal to merge into trunk. The outcome,
> if approved, would be substantially different. I don't think
> "superseded" would make sense here.
>
> 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?
>
> Aaron

So I won't say that all proposals to release supersede proposals to
merge to trunk. I mostly wanted a way to close my proposal in a clean
way, as I didn't mean to make it.

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.

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.)

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqVbBIACgkQJdeBCYSNAAP5EgCbBBNAqaE3pq2st9ijEauE7g2x
TfcAoInKyAlfzhuZulxlk+5O0AoL91AI
=RTS9
-----END PGP SIGNATURE-----