On 10/28/2010 7:16 AM, Martin Pool wrote:
> Thanks for the report. There are other similar bugs in other commands.
>
> Perhaps we should check for a 'reliable' user id only in commit?
I believe the trigger is that bzr wants to be able to annotate the
working copy for any changes relative to the basis, and be able to label
those lines as modified by you.
We could fall back to something else if we can't determine a valid "whoami".
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
On 10/28/2010 7:16 AM, Martin Pool wrote:
> Thanks for the report. There are other similar bugs in other commands.
>
> Perhaps we should check for a 'reliable' user id only in commit?
I believe the trigger is that bzr wants to be able to annotate the
working copy for any changes relative to the basis, and be able to label
those lines as modified by you.
We could fall back to something else if we can't determine a valid "whoami".
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkz JdUAACgkQJdeBCY SNAAPqSQCfUhnSn GApYxPjfIIa793H XMls s1QVC96eJOznOH1 Yk1
Z3UAoIT6l9rVF+
=5kbI
-----END PGP SIGNATURE-----