>>> Okay but now I have another question. I want to use zfs snapshot/clone to >>> clone a ON build level. Here's what I'm trying to do: >>> >>> zfs create pool/willf/hg/i386/onnv_94 >>> g clone -r onnv_94 /net/elpaso.eng/export/gate-hg onnv_94 >>> abort: destination 'onnv_94' already exists >> >> cd <that filesystem> >> hg init >> hg pull -u -r onnv_94 ... >> hg reparent ... > > A couple things in regards to the above. After I did the initial: > > hg pull -u -r onnv_94 /net/elpaso.eng/export/gate-hg > > I then did: > > $ hg pull -u -r onnv_94 ssh://onnv.sfbay.sun.com//export/gate-hg/usr/closed > remote: Not trusting file /export/gate-hg/usr/closed/.hg/hgrc from untrusted > user daemon, group other > pulling from ssh://onnv.sfbay.sun.com//export/gate-hg/usr/closed > searching for changes > abort: repository is unrelated > remote: Not trusting file /export/gate-hg/usr/closed/.hg/hgrc from untrusted > user daemon, group other
Because you're still in your gate repository. Either of the following should work. If you have not yet hg init'd in usr/closed, then % cd usr % hg clone -r onnv_94 ssh://onnv.sfbay.sun.com//export/gate-hg/usr/closed or if you have already created your closed repo, then % hg -R usr/closed pull -u -r onnv_94 > And second (on snv_88): > > $ hg reparent ssh://onnv.sfbay.sun.com//export/gate-hg > hg: unknown command 'reparent' The reparent command is part of the Cadmium extension. Are you loading that in your .cshrc? Check the hgsetup(1) manpage. > So how does this work when I need to pull from two different > repositories? Two separate operations. Hg will never do it for you implicitly. --Mark
