[p4] File modtime confusion
jjensen at apache.org
Wed Aug 29 19:12:22 PDT 2007
Perforce does not overwrite "writable files". If a file is writable in your
workspace, whether opened for edit or not, Perforce will not overwrite it
(ignoring the +w attribute... :-).
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Dave Lewis
Sent: Wednesday, August 29, 2007 6:15 PM
To: Paul Goffin
Cc: Mark Lee; perforce-user at perforce.com
Subject: Re: [p4] File modtime confusion
On 8/29/07, Paul Goffin <paul.goffin at dsl.pipex.com> wrote:
> I think you'll find the file isn't changed at all - the sync doesn't
> actually happen.
> I can't remember exactly why Perforce works this way but it makes sense
> you've heard the explanation. (I'm sure it's documented.)
if you have it open for edit, syncing a new version will overwrite
your changes. Remember that perforce hardly ever actually looks at
your files, it just sends you what its records indicate you need. Its
records indicate you're editing that file, or, at the very least, you
want to edit *that version* of the file,otherwise you'd revert, sync
and open for edit another version.
To have it 2nd guess your intentions would be confusing and inefficient.
> >Does anyone know why the file modtime is not changed when a file opened
> >is synched to a previous version? This is not what I would expect.
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.484 / Virus Database: 269.12.10/977 - Release Date:
> perforce-user mailing list - perforce-user at perforce.com
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user