question regarding mercurial
dhruvakm at gmail.com
Wed Mar 5 23:46:24 CST 2008
On Thu, Mar 6, 2008 at 1:41 AM, Mohit Aron <extproxy at gmail.com> wrote:
> One can always setup one's workspace such that the code is on NFS, but the
> binary files produced by the compiler go to the local disk.
1. Your repository is on an NFS mounted disk and hence the ".hg"
folder too is on the remote disk?
2. Suppose, we come up with an extension "hg edit", should it store
the edit information in the remote ".hg" or create it on the local
disk (make it configurable)
A simple hack I can think of:
1. Have a shell alias (or a new hg command) to write the edited file
path into a file
2. On hg commit, read the file with edited file paths and commit only
those files (by passing the files as arguments to the hg commit)
would the above approach work for you?
Contents reflect my personal views only!
More information about the Mercurial