[patch] Use /etc/mailname if available
Aaron Bentley
aaron.bentley at utoronto.ca
Wed Dec 21 07:42:03 GMT 2005
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
James Blackwell wrote:
| 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 recently had a conversation with someone in IRC who wanted to edit his
revisions because they had the wrong committer ID. I told him 'No!
That's forbidden by the model!' And I got this sense of deja vu, as if
I was still working on Arch.
I think it's irritating, at the very least, for bzr to store
likely-wrong information in perpetuity. It doesn't seem fair to the
user, who might be quite willing to correct it, given a warning. And
there have been situations in which I thought the committer ID was set
correctly, but it was not. Those bugged me.
| 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.
I dig that. It's very nice to be able to say there's no step 4. We
could simply set it the first time out, and tell the user what we'd done.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDqQdL0F+nu1YWqI0RAsa1AJ4oRYdIauH6V+LIJLMZ0VSUqHDi5gCfX37H
YA3gmF46dL/u+YuahJIXFK0=
=QVqZ
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list