submit direct + overwrite + no get latest = revert

Andy Knipp

This bit us on our config branch.

One person renamed a directory and just did a submit direct to clean up, with overwrite.

View modified showed only the rename, HOWEVER since they had not done a get latest, it REVERTED all the changes in Staging back the version his workarea had.


So, how can I prevent this in the future ? No question he should have view_modified, selected the changes and submitted. Compare will not allow you to submit, that would have shown the conflict. I do not want to turn off submit_direct (since that is role based, if he loses it so do I)

I am rather surprised that this does not pop up a warning, even with overwrite on.

If I edit an old file, it gives me a warning & makes it very hard to step on someones changes. Why is this so easy ?

Here is a fun test, (on an OLD branch) create a WA off an old edition. Do a list modified (shows nothing), click overwrite and submit direct. It will tell you conflicts are overwritten, but it will also revert all changes.

This stinks like a bug since, if I make a change and submit direct (without the overwrite flag) only my modified files go. But if I use the overwrite flag, EVERY difference goes.

Call me stupid, but the overwrite filag should not expand or change the list of files to be submitted. It should, when there are conflicts, automatically push the changes.

Still cleaning up the mess....

Andy