Thomas Eliassson writes:
>
> I've tried it out, it DOES work the way I described.
> At least when I do it the straight forward way using WinCVS 1.2
> accessing our CVS server 1.11 on Solaris.
Perhaps WinCVS does something peculiar -- standard CVS behaves as I
described.
-Larry Jones
That's one
WinCVS or
Solaris CVS (which one is setting rev no?).
I guess it will work fine for us anyhow, since we don't need to bother
about revision numbers now that we're using CVS, and pre-CVS files will
still be possible to trace using the revision numbers.
/Thomas
> Subject: Re
Thomas Eliassson writes:
>
> This also means that it's perfectly ok (even preferred) for new files to
> be numbered with 1.1, as long as I can still track files from before we
> had CVS. I also checked that this is the way it works (at least with our
> CVS setup), so if one file in the directo
>>On Tue, Jan 29, 2002 at 01:46:52PM +0100, Thomas Eliassson wrote:
>> Now when we start using CVS I see that we can
>> use 'cvs commit -r2.4 file.txt' to commit a file with a specific
>> revision number (in the example 2.4). Is this safe, or may we run into
>> some trouble later on?
>
> This
Eric Siegerman writes:
>
> Because CVS provides no way to specify that new files should get
> a major revision number other than 1, people have to remember to
> do it manually. *Every* time. If they forget -- and they will,
> being human -- your revision-numbering scheme goes out the
> window.
On Tue, Jan 29, 2002 at 01:46:52PM +0100, Thomas Eliassson wrote:
> Now when we start using CVS I see that we can
> use 'cvs commit -r2.4 file.txt' to commit a file with a specific
> revision number (in the example 2.4). Is this safe, or may we run into
> some trouble later on?
This is safe, i
Thomas Eliassson writes:
>
> The major revision number (i.e. 1 in 1.3) may in some of our files be
> increased to 2 or even 3. Now when we start using CVS I see that we can
> use 'cvs commit -r2.4 file.txt' to commit a file with a specific
> revision number (in the example 2.4). Is this safe,
Hi!
I know that one shouldn't care about revision numbers in CVS, but since
we want to be able to trace old revisions of files, from before we
started to use CVS, we'd like to 'mess' a little with them. The question
is if it's safe.
The major revision number (i.e. 1 in 1.3) may in some of our
