[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-dev
Subject:    Re: [Python-Dev] Mercurial?
From:       Dirkjan Ochtman <dirkjan () ochtman ! nl>
Date:       2009-04-07 6:15:33
Message-ID: ea2499da0904062315j3a535077w387ce1323ad81a1b () mail ! gmail ! com
[Download RAW message or body]

On Tue, Apr 7, 2009 at 00:05, "Martin v. Löwis" <martin@v.loewis.de> wrote:
> I think the identification in the SSH keys is useless. It contains
> strings like "loewis@mira" or "ncoghlan@uberwald", or even multiple
> of them (barry@wooz, barry@resist, ...).

Right, so we'll put up the author map somewhere with the email
addresses I gathered and ask for a more thorough review at some point.

> It seems that the PEP needs to spell out a policy as to what committer
> information needs to look like; then we need to verify that the proposed
> name mapping matches that policy.

Right. It's basically "Name Lastname <email>" -- we can verify that in a hook.

> Correct. The objective was to not allow nick names, but have real names
> as committer names. It appears that this policy does not directly
> translate into Mercurial.

One of the nicer features of Mercurial/DVCSs, in my experience, is
that non-committers get to keep the credit on their patches. That
means that it's impossible to enforce a policy more extensive than
some basic checks (such as the format above). Unless we keep a list of
people who have signed an agreement, which will mean people will have
to re-do the username on commits that don't constitute a non-trivial
contribution.

Cheers,

Dirkjan
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-dev%40progressive-comp.com

[prev in list] [next in list] [prev in thread] [next in thread]