I consider myself to be a beginner when it comes to revision control so bare with me if these questions and thoughts sounds silly.
What I am trying to figure out is how to handle patching in a project using subversion. Let me explain it like this:
Say that I have a project in trunk that looks like this:
Code:
MyProjektDir
|
|
---- DirOne
| |
| |
| ---- FileOne.php
| |
| ---- FileTwo.php
|
---- DirTwo
| |
| |
| ---- FileThree.php
|
---- FileFour.txt
|
|
---- FileFive.php
I have made a tag on the whole project and called it "Release 1.0".
Now I realize that I need to make an adjustment to FileTwo.php and FileFive.php to fix a bug.
Now, in order to not have to extract the whole project to fix the installation, I would like to only check out the two files that I have made changes to. Basically I want to create a "patch" containing FileTwo.php and FileFive.php.
Then eventually, when further changes have been made to the project I will tag the whole thing and call it "Release 2", where the "patch files" of course will be included.
So, I guess my question is: How do you handle these situations? Is it possible to tag only a part of a project and call it eg "patch 1" so that I can easily find the two files that I need?
It is my understanding that this is not possible to do in subversion, so how should I handle this?
I have read that in subversion "every revision is a tag" which leads me to believe that I must always tag the whole project. Are there other revision control software available that handle these types of situations better, or am I just simply handling this the wrong way?
Any advice is much appreciated!