Gordon Tyler wrote:
> ** Also affects: bzr
> Importance: Undecided
> Status: New
>
I think we would be okay with a flag that allows patches to be 'dirty',
but I think we also would like a way to force them to be pristine.
I don't remember exactly where handle-patch is used, but there are some
places (I believe) where we emit the diff and then parse it later, and
we'll want to make sure they match exactly.
I didn't look at the patch, but it would be nice if the decision to be
lenient could be turned on/off.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gordon Tyler wrote:
> ** Also affects: bzr
> Importance: Undecided
> Status: New
>
I think we would be okay with a flag that allows patches to be 'dirty',
but I think we also would like a way to force them to be pristine.
I don't remember exactly where handle-patch is used, but there are some
places (I believe) where we emit the diff and then parse it later, and
we'll want to make sure they match exactly.
I didn't look at the patch, but it would be nice if the decision to be
lenient could be turned on/off.
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
ZuGIACgkQJdeBCY SNAAPCGwCeOAYDg ZUq9aNEBsK594BK NEV5 pNXkIo87GVlg3AW L+
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkt
05IAnRenOnyMe9+
=V+lD
-----END PGP SIGNATURE-----