mercurial notifications

[Kelly O'Hair]

Humm...

Anything in the [ui] username will be put into any changesets created
by that user (e.g. hg commit or hg tag), verbatim, as a permanent record.
In the OpenJDK project we insisted on people setting username to the
OpenJDK name that you registered as, and ONLY that name.
We were concerned about email addresses getting buried in the changesets
and providing too much of a source of valid email addresses for spambots.

Does the [email] settings not work? e.g.

[email]
from = your at email.address

Seems like it should.

-kto

Mark Wielaard wrote:
> Hi all,
> 
> On Thu, 2008-09-25 at 14:45 +0200, Mark Wielaard wrote:
>> On Sun, 2008-08-31 at 21:01 +0100, Andrew John Hughes wrote:
>>> On 31/08/2008, Mark Wielaard <mark at klomp.org> wrote:
>>>> You managed to push this without generating a commit message. I cannot
>>>>  figure out why that is. Do you have any idea how you got this commit in
>>>>  "under the hgext.notify radar"?
>>>>
>>> Something is broken:
>>>
>>> remote: added 1 changesets with 2 changes to 2 files
>>> remote: error: incoming.notify hook raised an exception: cannot
>>> concatenate 'str' and 'NoneType' objects
> 
> We finally found it!
> The issue is when your hgrc doesn't contain an email address.
> So please make sure that your ~/.hgrc contains at least the following:
> 
> ### --- User interface
> [ui]
> ### username data to appear in comits
> ### it usually takes the form: Joe User <joe.user at host.com>
> username = My FullName <me at example.com>
> 
> If for some reason you need your global ~/.hgrc to contain something
> else than your full name then add this to your project specific hgrc:
>   icedtea/.hg/hgrc
>   icedtea6/.hg/hgrc
>   icepick/.hg/hgrc
>   pulseaudio/.hg/hgrc
> etc.
> 
> That way your commits will always have a full name plus the email
> address added. Which will then be used to send to notification emails to
> the mailinglist.
> 
> Thanks,
> 
> Mark
>