"Mateusz [PEYN] Adamus" wrote: > > Hi. <SNIP> > 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? > Tag them all (whole project). Why: 1) you almost never know when you start fixing a problem ALL the files that will be affected. 2) when you do a checkout against a normal tag, you only get those files that have been tagged with the named tag. 3) it is easier, you don't have to figure out what to tag, you just DO IT(tm) :).
side note: If your repository contains files that are not used in specific circumstances, you can use why #2 to have a baseline tag that only gets the files needed for the circumstance. I have used this to my advantage on a couple of projects. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
