http://sandhillcreative.com/kb/2010/04/28/mercurial-pushing-changes-to-a-remote-site/ Wed, 14 Mar 2012 23:45:54 +0000 hourly 1 http://wordpress.org/?v= http://sandhillcreative.com/kb/2010/04/28/mercurial-pushing-changes-to-a-remote-site/comment-page-1/#comment-67 Stuart Thu, 02 Sep 2010 18:01:32 +0000 http://sandhillcreative.com/kb/?p=224#comment-67 Thanks Ethan. This is a good point that I wasn't aware of. Thanks Ethan. This is a good point that I wasn’t aware of.

]]> http://sandhillcreative.com/kb/2010/04/28/mercurial-pushing-changes-to-a-remote-site/comment-page-1/#comment-66 Ethan Thu, 02 Sep 2010 17:51:29 +0000 http://sandhillcreative.com/kb/?p=224#comment-66 You can also add trusted.users=root in /etc/mercurial/hgrc, and that should enable root-trust of hgrc files in individual repositories hosted on that machine. As an administrator for a central repository, this is much easier than begging each user to please add a trust setting for your machine, and also avoids having them trust everyone (as suggested by users=* in your solution) You can also add trusted.users=root in /etc/mercurial/hgrc, and that should enable root-trust of hgrc files in individual repositories hosted on that machine. As an administrator for a central repository, this is much easier than begging each user to please add a trust setting for your machine, and also avoids having them trust everyone (as suggested by users=* in your solution)

]]>