I think considering the machine's mailname is perhaps not necessary.
As I see it, there are two significant divisions of use-cases here:
1) The ones that bug 549310 was filed about, where users are committing revisions to be shared with the world, and the email address really really ought to be a valid configured email address.
2) The ones who are managing an /etc-in-bzr, where <local-unix-user@machine-hostname> is probably the exact most useful thing that we could record anyway.
Could we not just add a branch.conf boolean setting (and corresponding switches to 'bzr init', 'bzr reconfigure') which reverts to the previous behaviour?
I think considering the machine's mailname is perhaps not necessary.
As I see it, there are two significant divisions of use-cases here:
1) The ones that bug 549310 was filed about, where users are committing revisions to be shared with the world, and the email address really really ought to be a valid configured email address.
2) The ones who are managing an /etc-in-bzr, where <local- unix-user@ machine- hostname> is probably the exact most useful thing that we could record anyway.
Could we not just add a branch.conf boolean setting (and corresponding switches to 'bzr init', 'bzr reconfigure') which reverts to the previous behaviour?