|
From: | Mateusz [PEYN] Adamus |
Subject: | Bug fixing and CVS tagging |
Date: | Tue, 02 Aug 2005 12:39:13 +0200 |
User-agent: | Mozilla Thunderbird 1.0 (Windows/20041206) |
Hi.I'm fairly new to CVS. I've been using it for a couple of months now but mainly all I've been doing is CO and commiting files. Now I'd like to take a next step and use CVS's more advanced features. I branched my project before release, tagged it to be able later to retrieve release and original files of branch.
Now what I'd like to do is to fix some bugs in my release. No problem with that. I'm onlu concerned about tagging files. I read somewhere that it is a good practice to tag files before and after fixing a bug. Thanks to it later on I will be able to retrieve what exactly have been changed to fix what bug.
OK. Thats great. But what files should I tag? Only those that I will change during fixing a tag or maybe a hole project? What is a good practice in this scenario? And why?
best regards Mateusz [PEYN] Adamus
[Prev in Thread] | Current Thread | [Next in Thread] |