On 4/23/10 11:09 AM, Goswin von Brederlow wrote:
For SVN users it gets much worse: vi existing-file.c # do some changes vi new-file.c # create the file git add new-file.c vi new-file.c # do some more changes git commit A SVN user would expect the current working copies of existing-file.c and new-file.c to be commited. Instead only new-file.c is commited and only the fist modification.
But is compatibility with the SVN interface really what we want to aim for? Just because their interface works that way doesn't mean it's the correct way.
tom -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html