[patch] Use /etc/mailname if available

[James Blackwell]

On Mon, Dec 19, 2005 at 09:27:59AM -0500, Aaron Bentley wrote:
> I think it uses it because it's conventional to have a committer field
> in commits, and so it guesses the best one it can.  I don't think it was
> ever about unique ids.
> 
> We could just require the user to set an email address if bzr can't find
> a reasonable one (e.g. by checking EMAIL), but that would turn our
> 3-step startup into a 4-step one.  But using the wrong committer ID is
> perhaps serious enough that we should do it.

I'm in favor of guessing even if wrong. Users don't seem to care much
about the committer field until they get into merging. Once they
get to that point they can fix it then.

I frequently talk to random() person and open up with:

  cd code; bzr init; bzr add; bzr commit -m"My code is controled"

That's powerful when talking to cvs users that after 3 years _still_ can't
quite figure it out. This is such a useful thing that at one point I
considered suggesting we implement a -m option that would implicitely run
add:

  cd code; bzr init -m"My code is controlled"

  bzr: Your project has been auto imported. xx files were ignored.