I'm totally lost here with branching.

What I'm trying to do is: Take the complete state of a directory and create a (lazy) snapshot of it in a different path. That destination path will be updated in-place. The update should produce exactly the same content that was in the source at some given time specified by a changelist number.

What I do is: - Get highest submitted CL (that's my time ref) (call it TopCL) - Create a new CL (becoming the container for integ revs) (call it ResTL) - "p4 integ -t -d -c <ResTL> //originpath/...@<TopCL> //mirrorpath/..." - "submit -c <ResTL>"

This works nicely in my test bed, but gives me hilarious merge conflicts in the production env and fails to add new files. I don't get it.

If I'm going to branch off a specific version, overwriting the mirror which was never touched since the last version, what do these conflicts mean, how to prevent them? I don't get any conflicts with my test server.

I'd like to do this in a cron job, so it definately has to run fully automated.

Best regards,

"Wenn ich Visionen habe, gehe ich zum Arzt." - Helmut Schmidt