Mercurial Checkins

Question

Is there any way to verify / authenticate checks in Mercurial? I would like to release HG through our organization (more than 60 developers), and I would like all the checks to be on the right user and that they are all in the correct format.

During the tests, we found that some users registered under completely different user names (copied a different user’s .hgrc file) and others who were registered in several different versions of their name (name, full name, email address, etc.) using different clients.

We could add a hook to provide a username format, but it still does not guarantee that it is the correct user. Does Mercurial have anything to deal with, or am I just stuck in CVS / SVN thinking?

Thanks, Dave.

Answer 1

Mostly you work with CVS / SVN thinking - if your employees are dishonest, you are screwed up anyway. :) However, there are several ways that other people have handled this using various methods:

• mozilla and some others have added a visible pushlog that shows who moved each cset to each repo, so you get an implicit statement step along the way.
• gpg, , csets changegroup, , csets .
• , $REMOTE_USER ( http) $USER ( ssh) , push-ing.

, .

, , ( ) . , , ( ..), , , .

Answer 2

-, , , .

, , , cset, ( http ssh). , , .

pgp ( hgext) , , .

commitsigs - , . , . 2 .

Mozilla pushlog, , . ( ), , , , . , , push ( , Python ).

, . , : . , . , , ?