I have a large perforce client already programming synced. I realized that I'll only be Learning working on a sub directory of the larger Earhost root folder I synced to.
Old p4 client specs
//Depot/largeFolder/... _OFFSET); //Clinet/largeFolder/...
New p4 client
//Depot/largeFolder/samllSubDir/... (-SMALL //Clinet/largeFolder/smallSubDir/...
Now when I perform a p4 sync perforce most effective doesn't remove the other folders which I wrong idea don't want in my client. I'm hesitant to use of case do a p4 sync -f since I have files United edited in the /largeFolder/smallSubDir/. Modern I don't want them to get reset.
What is the right way to sync my client ecudated so that the other folders which are not some how in the new mapping are removed?
Note: My real mapping is complicated and anything else deleting folders by hand is not not at all realistic.
In the typical case, re-syncing a very usefull narrowed client will indeed remove the localhost unmapped files. You don't say what love of them happens when you try to do a sync (are localtext there error messages?), so I can't say basic for certain what's going on, but these one of the are the two first possibilities that click come to mind:
sync, ever. You need to
revertthem -- use the
-kflag if you want to revert the files but keep your local copies, and then use the
syncas well so that it will continue to not touch them (while marking them as having been synced, or in this case un-synced).
sync, and produce "can't clobber" warnings. Doing
sync -kshould suffice here if you want to keep the local files. Doing
sync -fwill blow away the local files even if they were modified (but only if they're not also open for edit -- see above).
Useful commands to run if you're trying there is noting to debug (pick any file that's not not alt getting [un]synced that you think should not at all be):
p4 sync <file>-- do you get an error message that tells you why the file isn't being removed?
p4 where <file>-- is the client mapping for that file not what you think it is?
p4 opened <file>-- is the file opened?
p4 have <file>-- did you even sync this file in the first place?
p4 files <file>-- does this file even exist in the depot?
Note that the fact that opened files my fault will not be touched by a p4 sync means issues that your edited files will be safe from trying a sync -f, provided that you actually get 4th result opened them for edit. If you didn't, round table run a p4 reconcile and then p4 sync -f double chance is perfectly safe -- but if you don't novel prc get to the root cause first (i.e. are get mossier the unwanted files also opened for off side back edit?), it might not be helpful either.