[ On Wednesday, December 3, 2003 at 12:36:35 (-0600), [EMAIL PROTECTED] wrote: ]
> Subject: Re: CVS Version CHange
>
> Could be. The RCS revision number looks too much like a standard sort
> of release designation, and that leads to trouble. It appears to
> contain more info
Greg Woods:
>
> In CVS the release number of RCS-Id is like any useless and almost
> atrophied organ -- however it's impossible to give it up without
> also giving up backwards compatability of the internal repository
> structure.
>
It also is necessary as a "magic cookie" - an otherwise meaningle
Jim.Hyslop writes:
>
> If that's the case, then why was the revision number ever exposed in the
> first place? Is it a legacy of RCS or SCCS - do they not support symbolic
> tags?
I cannot say for sure, but presumably it's exposed in CVS because it was
exposed in RCS, which was the model (as well
[ On Tuesday, December 2, 2003 at 10:47:46 (-0500), Jim.Hyslop wrote: ]
> Subject: RE: CVS Version CHange
>
> If that's the case, then why was the revision number ever exposed in the
> first place? Is it a legacy of RCS or SCCS - do they not support symbolic
> tags?
I don&
[ On Monday, December 1, 2003 at 10:18:19 (-0500), Jim.Hyslop wrote: ]
> Subject: RE: CVS Version CHange
>
> On the other hand, the developers may want to take the current state of the
> repository, and assign it a known starting point, such as 2.0. This is
> entirely reasonable
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] wrote:
[specifying revision numbers on checkin - is it reasonable?]
> No, it is not. Revision numbers are for CVS's internal use
> only;
If that's the case, then why was the revision number ever exposed in the
first place? Is it a legacy of RCS or SCCS
Jim.Hyslop writes:
>
> On the other hand, the developers may want to take the current state of the
> repository, and assign it a known starting point, such as 2.0. This is
> entirely reasonable.
No, it is not. Revision numbers are for CVS's internal use only; people
should ignore them and resist
Mark D. Baushke [mailto:[EMAIL PROTECTED] wrote:
> S.Magesh <[EMAIL PROTECTED]> writes:
> > Is there any way to change version in existing repository
> i.e i have a
> > repository name MAC , in this repository the version of the
> files are
> > 1.3,1.4 etc ... , Now our project developers are ask
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
S.Magesh <[EMAIL PROTECTED]> writes:
> Dear Sirs,
>
> Is there any way to change version in existing repository i.e i have a
> repository name MAC , in this repository the version of the files are
> 1.3,1.4 etc ... , Now our project developers are ask
On Wed, 23 May 2001, Anders Truelsen wrote:
> > I need to change the version of one of my CVS files, as the
> > version should
> > be used later in the release version using an automated script.
>
>
> I don't get that. The revision number chanhges when-ever you change your
> file, otherwis
> I need to change the version of one of my CVS files, as the
> version should
> be used later in the release version using an automated script.
I don't get that. The revision number chanhges when-ever you change your
file, otherwise you really should leave it alone, it is _not_ recommendab
Dirk Stoecker <[EMAIL PROTECTED]> writes:
> Hi,
>
> I need to change the version of one of my CVS files, as the version should
> be used later in the release version using an automated script.
>
> The "Open Source Development with CVS"-book only states, that this is
> seldom used and not explai
12 matches
Mail list logo
