[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Versioning help after Tagging required.

From: Eric Siegerman
Subject: Re: Versioning help after Tagging required.
Date: Mon, 4 Jun 2001 18:57:11 -0400
User-agent: Mutt/1.2.5i

On Mon, Jun 04, 2001 at 05:07:56PM -0500, address@hidden wrote:
> "Sonya Iyer" <address@hidden> wrote:
> > I want to bring my entire
> > module to have a version 1.3, so that changes to any file from here
> > on forth will be 1.4 (or and so on...)
> You might want to just ignore the RCS revision numbers (1.3,,
> etc.) -- just consider them to be an internal implementation detail of
> CVS -- and just use your tags to refer to the versions you want.

I'd word that more strongly.  You REALLY SHOULD ignore the RCS
revision numbers; "cvs commit -r" is a place you almost certainly
don't want to go.

For example, what happens when you add a new file,  It'll
go in at revision 1.1 unless the person adding it remembers to
give the right "-r" option for whatever "module revision" is
appropriate at the moment.  And they have to remember the "-r" at
commit time, which may be quite a while after they "cvs add"ed
the file.  It's easy to forget to do this; thus, any process that
depends on it is bound to be fragile.

Use CVS tags instead; it's what they're for.


|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea.
        - RFC 1925 (quoting an unnamed source)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]