On Wed, Jul 16, 2008 at 01:37:33PM -0700, Stephen Lau wrote: > I would really recommend using ssh instead of NFS.
The flag day only mentioned NFS access. I tried switching '/net/elapso.eng/export/gate-hg' to 'ssh://elpaso.eng/export/gate-hg', but now I gate: remote: abort: There is no Mercurial repository here (.hg not found)! abort: no suitable response from remote hg! How do I get ssh to work? > You can also put: > [trusted] > groups=other > > in your ~/.hgrc to get that noise to go away This did get the noise to go away. However, if the flag day documented the NFS path as the only internal option, then it seems like this should be a mandatory thing as well. It's also annoying that simple actions like 'hg status' on an untouched workspace take over 5 seconds, but I assume that's just an artifact of the mercurial architecture. - Eric -- Eric Schrock, Fishworks http://blogs.sun.com/eschrock
