> 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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 enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkq Vad4ACgkQ0F+ nu1YWqI1XJwCfYG rJiXQv/ DA1HtPcWtiXm6XW OK7E/+VMndtoA0H DxKZk
o3QAmwTrIcd+
=r8EM
-----END PGP SIGNATURE-----