I have a Mercurial repository on my laptop which I clone locally to
make code changes, these changes are committed locally and
periodically groups of changes are pushed back into the 'master'
repository. This works well.

Last night I set up a new clone of the repository on a NAS drive. My
Mac automatically reconnects to the NAS drive when I log in. The NAS
repository will be accessed by a Hudson installation on another Mac on
the network to build and deploy into a sandbox, so that the current
working version of the application is always available to play with.

Having set up the repository in the normal manner (hg clone) last
night I've tried to push changes to it today, only to receive the
following message:

pushing to /Volumes/mercurial/content-api
abort: No such file or directory: /Volumes/mercurial/content-api/.hg/
store/lock

And yes, looking in /Volumes/mercurial/content-api/.hg/store, there is
no file or directory called 'lock'. Any suggestions?

--

You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.


Reply via email to