Martin Pool wrote:
> I think the main thing here is
>
> * it doesn't actually benefit 2.0 users
> * it makes the diff bigger for people to read in the next SRU
> * any code change, even mechanically, has some small risk
>
> I tried to explain this more in https://code.edge.launchpad.net/~mbp/bzr/doc/+merge/16997
I had forgotten about the need to have a bug for SRU purposes.
Generally, I try to target anything small to 2.0, because otherwise my
default behavior is to just do everything in 'dev' and then nothing gets
into 2.0.
I'll just land this in 2.1.
merge: rejected
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
Martin Pool wrote: /code.edge. launchpad. net/~mbp/ bzr/doc/ +merge/ 16997
> I think the main thing here is
>
> * it doesn't actually benefit 2.0 users
> * it makes the diff bigger for people to read in the next SRU
> * any code change, even mechanically, has some small risk
>
> I tried to explain this more in https:/
I had forgotten about the need to have a bug for SRU purposes.
Generally, I try to target anything small to 2.0, because otherwise my
default behavior is to just do everything in 'dev' and then nothing gets
into 2.0.
I'll just land this in 2.1.
merge: rejected
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
HXqUACgkQJdeBCY SNAAM7HwCeJ0kQ4 ybnsxLbO7JItlnJ Xyv5 sUowPGO4w6EwovP 0v
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkt
n8MAnRzNCbfTBRU
=XA3T
-----END PGP SIGNATURE-----