Re: P4 Sync problem

From: Dmitry Smirnov <divis1969@gmail.com>
Date: Nov 11, 2009, 14:57 UTC
Message-ID: <loom.20091111T154425-182@post.gmane.org>
In-Reply-To: <1a6be5fa0911110554u7c3a04c8hf50100b784b63c7a@mail.gmail.com>

Tor Arvid Lund <torarvid <at> gmail.com> writes:

Show 12 quoted lines

> //depot/A/...
> -//depot/A/B/...
> //depot/A/B/C/...
> 
> ... git-p4 sorts these paths by length. For a given filename, it finds
> the longest path that matches that files directory, and if that path
> starts with a '-', the file is not synced (for a file
> "//depot/A/B/myfile.c" it gets a match on "-//depot/A/B/...", and
> myfile.c is not synced, but the file "//depot/A/B/C/myotherfile.c" it
> matches "//depot/A/B/C/...")
> 
> Do you have an example that shows how it might fail?

According to the P4 User's Guide (http://www.perforce.com/perforce/doc.091/manuals/p4guide/02_config.html#1066090) Perforce prefer later mapping if there is a conflict.

So, if you switch paths: -//depot/A/B/... //depot/A/... perforce will sync all the the files. Of course, this is not a very useful case. I suppose the order is not important until mapping are implemented...