[p4] Sync updates the revision number of open files

[Stephen Vance]

Perforce won't let them submit that file without resolving the merge. 
For users, that will be a big red flag.

For automated processes, just scan the output for the warning. You can 
even do a 'sync -n' to test it first.

Given these suggestions, I don't understand what the problem really is. 
How does this behavior cause a problem?

But no, there isn't any way to prevent this that I know of.

Steve

Robert McKenna wrote:
> Hi
> I having a problem in which users who have a file open for edit at say
> revison 10, sync to a newer without submitting their changes. This does
> not overwrite the users changes but does update the revision number in
> the changelist and client view while scheduling the file for resolve. A
> warning is issued in the command output, which is easy miss when syncing
> large numbers of files, particularly as we use automated update tools
> and also have integrations that require extensive manual merging. This
> leaves the user confused to say the least.
>  
> Does anyone know how to prevent this? It is technically user error but
> in our situation is almost certain to happen on a regular basis.
>  
> Rob McKenna
>  
>  
>  
>  
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>