ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Walker Joe <>
Subject RE: Perforce task and Source Code Control
Date Tue, 17 Oct 2000 13:41:42 GMT


Just back from holiday in Ireland, sorry about the delay.

force='true' effectively adds the -f flag to the p4 sync command
% p4 help sync
        Normally, sync will not clobber files in the client workspace that
        the user has made writable.  Setting the 'clobber' option in the
        client spec disables this safety check.

        The -f flag forces resynchronization even if the client already
        has the file, and clobbers writable files.  This flag doesn't affect
        open files.

Do you think the description needs clarifying or maybe I'm missing something
more basic?


> -----Original Message-----
> From:	Diane Holt []
> Sent:	Friday, October 06, 2000 8:53 PM
> To:
> Subject:	RE: Perforce task and Source Code Control
> --- Walker Joe <> wrote:
> > Attached are 2 files - new version of the .java with re-written JavaDoc,
> > and an HTML file that simply contains the JavaDoc without the *s.
> > [...]
> > <p>syncs the files in the source directory that are in the
> > Perforce repository, as of change number 4513, overwriting any
> > modified files in the current source tree is needed.</p>
> Not sure what this sentence in the doc means -- 'p4 sync' will only
> overwrite modified files in the client tree if they're not officially
> 'p4 open'd and if you have "clobber" set on your client (if they -are-
> officially open'd, then it won't matter whether "clobber" is set or not,
> it still won't overwrite them).
> Diane
> =====
> (
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!

Legal Disclaimer:-

Please be aware that messages sent over
the Internet may not be secure and should
not be seen as forming a legally binding
contract unless otherwise stated.

View raw message