On 13/11/06 21:47, "Alan Dayley" <[EMAIL PROTECTED]> wrote:
> On the other hand, let me state the big picture. I am trying to solve > the problem of tracking branches. Our development team is relatively > small, we have fairly good communication and we strive to minimize the > number of active branches. However, when we make a branch and then 3 > months later need to understand why and where, I'd like to have an > easy way to point to the location of the branch within the context of > the overall project history. > > What are the practices others in the group use to solve this issue, if > not a tool that uses the data and meta-data from the repository? This rather chimes with my question about tagging and branches. I can come up with some system to tag files, but I feel I'm re-inventing the wheel, and - due to lack of experience - giving it corners! Examples of how a series of real tags and branches might look would be very helpful. And as Alan asks, what practices are there for recording it all. Thanks Roddie Grant _______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
