hg status issue on Windows with network servers
TK Soh
teekaysoh at gmail.com
Wed Mar 12 00:06:09 UTC 2008
On Mon, Mar 10, 2008 at 10:37 PM, Alexis S. L. Carvalho
<alexis at cecm.usp.br> wrote:
> Thus spake TK Soh:
>
> > We recently added a netapp file server that serve both Unix (NFS) and
> > Windows (CIFS) users. Naturally, I use Mercurial on both platforms.
> >
> > I mapped the server on XP (SP2) to drive X:, open a cmd window in a
> > repo that has been reported clean by 'hg st' on Unix (the repo has
> > been created and maintained on Unix), and entered 'hg st' command,
> > then a list of files showed up as being modified, while 'hg diff
> > --git' give an empty output. It turns out that these files have had
> > their executable permission bits enabled.
>
> The following patch should make this better, but you'll probably have
> some problems if you use "hg update -C" on windows and then try to use
> status/diff/commit on unix - hg won't show any file differences (which
> is fine), but if you change some executable file and then commit it,
> it'll probably silently lose the exec bit.
Just trying to understand this better, is hg writing different mode
data into .hg/dirstate if the file system does not support exec bits?
If this is true, can the exec bits be preserved in the dirstate data,
and only ignored on file systems that doesn't support exec bits in
dirstate.status(), andalso carry over during commit?
More information about the Mercurial-devel
mailing list