With regard to backing out checkins by submitting the older versions - what is the easiest way to do this? I just tried to do this for a user, and it seemed like a cumbersome process. - - sync to old revision - - copy to .bak - - sync to head - - edit - - overwrite the file from .bak and submit. - - ugh!

I suspect an edit, p4 print to overwrite, then submit might be better, but I haven't looked into this.

Also, and more speculative, consider the following situation: Program is being developed for two platforms, so users typically have two clients. Then when making changes on one of them, they would like to test the changes on the other, without, of course, checking the changes in. Do you guys have any suggestions or techniques that make this less error-prone or troublesome? I remember somebody suggesting branching, but this doesn't sound too palatable to me.

thanks!

dave