SVN commit single file or project folder
-
I am working on a VB.Net project and have been using SVN(tortise SVN) for version control. So far I have been making commits on the whole project folder so all files that have been changed are committed at the same time and the log comments apply to all the changed files . Is there any advantage in committing single files at a time when I have made changes to a group of source code files. Any advice on best practice would be helpful. This is the first project I put under version control that has really grown in file count size. Thanks, cages
-
I am working on a VB.Net project and have been using SVN(tortise SVN) for version control. So far I have been making commits on the whole project folder so all files that have been changed are committed at the same time and the log comments apply to all the changed files . Is there any advantage in committing single files at a time when I have made changes to a group of source code files. Any advice on best practice would be helpful. This is the first project I put under version control that has really grown in file count size. Thanks, cages
What you are doing is standard. I'm not aware of any advantage to committing single files. Sometimes other developers are waiting for your changes so that could be a reason. Best to complete a single task and commit before starting another task, if possible.
"You get that on the big jobs."
-
I am working on a VB.Net project and have been using SVN(tortise SVN) for version control. So far I have been making commits on the whole project folder so all files that have been changed are committed at the same time and the log comments apply to all the changed files . Is there any advantage in committing single files at a time when I have made changes to a group of source code files. Any advice on best practice would be helpful. This is the first project I put under version control that has really grown in file count size. Thanks, cages
It's been a few years since I used SVN (Tortoise SVN), but from what I remember is that SVN is actually quite good at posting only the necessary changes back to the repository each time you commit. For example, if you had a 100 line SQL script and you made 2 lines of change, the only thing that was actually stored back in SVN was the 2 lines of change. At least that is what I remember ... I could be wrong. Remember that you don't need to version control the binary files created by Visual Studio, only the source files. Storing of binary files may not be very efficient in SVN. My 2 cents. :)
-
What you are doing is standard. I'm not aware of any advantage to committing single files. Sometimes other developers are waiting for your changes so that could be a reason. Best to complete a single task and commit before starting another task, if possible.
"You get that on the big jobs."