|Subject:||svk ci with conflicts can lead to mistakes|
Consider the following scenario, a user makes local changes to a mirrored depot, the commit checks with the server and sees a conflict. The user is notified of the conflict and his commit message is saved in file svk-commitFOO (without any file list of what is to be committed). He then sync his depot and makes a few changes in other files to deal with the new commit. He then types `svk ci --file svk-commitFoo` intending to commit just the modified files he initially tried (and failed) to commit. Unfortunately, the result is that he accidentally commits everything modified in his local tree. I know that perforce avoids this mistake by moving changes from the default changeset to a numbered one upon commit attempt (even if it fails), so that the files involved will also be maintained. I think it would be nice if SVK did something similar.