[Nut-upsdev] Re: About CVS usage of tags and branches in NUT (was: CVS branches?)

Niels Baggesen nba at users.sourceforge.net
Wed Aug 17 07:35:17 UTC 2005

On Wed, Aug 17, 2005 at 08:47:25AM +0200, arnaud.quette at mgeups.com wrote:
> I hear you but:
> 1) tagging each release make redundancies with the existing patchs
> and tarballs (for each stable and testing, there's a patch _and_ a
> tarball). Looking at the CHANGES file help to see what has changed
> and when

That is not good enough when you want to see HOW it changed

> 2) the drop down list grows too quickly when tagging each stable/testing
> release, with a result that I don't like (too much info == loss of info).
> So I'll continue with the same process: No tags for stable and testing,
> and cvs tags for development.

I do not agree with you. It is absolutely vital, and one of the major
reasons for using a souce code control system, that you easily can
recreate ANY version, or check the differences between them.

There has to be a tag for each and every release, including pre-releases
/ release candidates.


Niels Baggesen - @home - Århus - Denmark - nba at users.sourceforge.net
The purpose of computing is insight, not numbers   ---   R W Hamming

More information about the Nut-upsdev mailing list