Tor Arvid Lund <torarvid <at> gmail.com> writes: > //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... -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html