Alexander Belchenko wrote:
> If this is no e-mail address then I doubt we should show it under E-mail
> section. Why for you need to specify something inside <>? Is not bzr
> should support the work without such address?
>
The specific request here was to use the user's standard username. So
they would give eg "jameinel" in that field.
My main complaint is that QBzr's config dialog isn't round-tripping the
information. I type:
Username: John Meinel
Email: jameinel
And I get back
Username: John Meinel <jameinel>
Email:
We could either:
1) Check and refuse things that don't look like an email address added
to the email field
2) Change internal bzr to return anything that is in <> as an "email"
3) Have a custom function in qbzr that does the same thing as (2)
instead of the bzr function.
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
Alexander Belchenko wrote:
> If this is no e-mail address then I doubt we should show it under E-mail
> section. Why for you need to specify something inside <>? Is not bzr
> should support the work without such address?
>
The specific request here was to use the user's standard username. So
they would give eg "jameinel" in that field.
My main complaint is that QBzr's config dialog isn't round-tripping the
information. I type:
Username: John Meinel
Email: jameinel
And I get back
Username: John Meinel <jameinel>
Email:
We could either:
1) Check and refuse things that don't look like an email address added
to the email field
2) Change internal bzr to return anything that is in <> as an "email"
3) Have a custom function in qbzr that does the same thing as (2)
instead of the bzr function.
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkq xKDEACgkQJdeBCY SNAAMA7QCeMsRaS x/kDgCUuHabqw5K 9npM rXtmFMmKnJQUi/ u+5
A5IAoJQAVh7xqAu
=A+7D
-----END PGP SIGNATURE-----