[p4] Problems with windows p4v
Stephen Vance
steve at vance.com
Wed Dec 5 18:52:20 PST 2007
Unless you have allwrite set, nothing synced on Linux should come out
with a 6.
As for your colleague's situation, it actually sounds like it's coming
out correctly. Things like execute bits won't be set because Windows
doesn't know about those, but the read-only nature is absolutely correct.
Under Linux, the umask will affect the permissions, but under Linux
mounted to Windows, the Linux export and the mount setting may affect
the permissions.
Basically, if preserving Unix permissions is important, you really need
to sync on Linux.
Steve
Steven W. Orr wrote:
> I mostly use the p4 commandline with a few things in done p4v, all under
> linux. Another person uses p4v under windows and his workspace is a linux
> directory. The problem that he is having is that the permissions on the
> files in the workspace are different from the permissions had he sync'd
> from linux. This is causing us a problem. Is there anything that we should
> be doing so that the permissions will match up to what they should be?
>
> In particular, everything is coming out with -r and +x. So as an example,
> something that should be a 644 or 664 is coming as 555.
>
> TIA
>
>
>
--
Stephen Vance
www.vance.com
More information about the perforce-user
mailing list