This is why Ian is using a version control system. As long as there are labels attached to each version, you can always go back and forward between versions without having to resort to different file names or different folders. As Ian explained, using?different filenames actually breaks this mechanism.?You may want to look into a Git tutorial to see how easy it is to - with just three or four commands you can do all that. All you need is to have Git installed on your system.?
To create a copy of the repository, you use this command (this assumes a Linux or other Unix type system - I don't know what the corresponding commands would be for Windows):
git clone?
You then go into the ubitx folder:
cd ubitx
From within this folder, you can list the tags that are?available:
git tags
If you want to use the latest version, you are usually already all set, to go back to a previous version, you would use?the checkout command:
git checkout v1.06
The argument you use (in this case "v1.06" is one of the tags that were listed with the "tags" command above).
You can always find out what's going on by using the "status" command:
git status
Especially if you?want to make your own changes, Git is a great system, because you will always know what you've changed and you can keep track of your changes by creating your own branches and tags.?
This is how professional software development is done.?
--
Karl Heinz - K5KHK
