On 11/05/2010 01:42 AM, Brad Crittenden wrote:
> Finally, it is clear you thought it out since you test for it explicitly, but I question the need to create a new merge proposal when nothing has changed. Do you have a good use case for that?
Actually, that was the existing functionality. It is for cases where
the proposal is marked "resubmit", many changes are made, and finally
the proposal is resubmitted.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/05/2010 01:42 AM, Brad Crittenden wrote:
> Finally, it is clear you thought it out since you test for it explicitly, but I question the need to create a new merge proposal when nothing has changed. Do you have a good use case for that?
Actually, that was the existing functionality. It is for cases where
the proposal is marked "resubmit", many changes are made, and finally
the proposal is resubmitted.
Aaron enigmail. mozdev. org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkz UJpAACgkQ0F+ nu1YWqI1WDwCdEK hJpAiuZXSzxf6/ PK5gmzGO rpfaDAegkFkU22z uN
wUUAnjmKdw60t5e
=houq
-----END PGP SIGNATURE-----