On Mar 25, 2009, at 11:03 AM, Gé Weijers wrote: > > Another issue is regulatory: sometimes you need to know who committed > what and when, for auditing purposes.
This is why I gave fossil the ability to PGP sign check-ins. If a check-in is PGP-signed, you have high confidence of who created it. There are also features to track when various artifacts were pushed to a server, to help track abuse. Of course, somebody can still create an unsigned check-in with a forged user-id. But in a regulatory environment, you simply ignore unsigned check-ins. Doesn't git also have the ability to PGP-sign check-ins? I seem to remember reading that, though I have never actually tried to do it. D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
