Re: The history of the Linux OS
Geert Uytterhoeven (Geert.Uytterhoeven@cs.kuleuven.ac.be)
Tue, 24 Nov 1998 14:02:43 +0100 (CET)
On Tue, 24 Nov 1998, Neil Conway wrote:
> Geert Uytterhoeven wrote:
> > On Mon, 23 Nov 1998, Simon Kenyon wrote:
> > > On 23-Nov-98 Geert Uytterhoeven wrote:
> > > >> say we have 1.1.1, 1.1.3, 1.1.4
> > > >> put them in cvs and all of a sudden 1.1.2 appears from some kindly soul
> > > >> can cvs/rcs/sccs (you choose) handle this?
> > > >
> > > > That's why we have tags. After checking in 2.1.129, you say
> > > >
> > > > cvs tag linus-2-1-129
> > > >
> > > > After that you can say
> > > >
> > > > cvs co linus-2-1-129
> > > >
> > > > to check out 2.1.129.
> > >
> > > i obviously didn't explain myself :-)
> > >
> > > i have 1.1.1
> > > i put it in rcs
> > > THEN i get 1.1.47
> > > so i put that in rcs
> > > NOW i get 1.1.x where 1 < x < 47
> > >
> > > how do i insert that inbetween 1.1.1 and 1.1.47?
> >
> > That's exactly the way you do _not_ want to do it. CVS doesn't care about the
> > internal RCS version numbers. Yes, I made the same mistake some time ago.
> > If a file isn't changed in between Linux release 2.1.128 and 2.1.129, it will
> > have the same (internal) RCS version number in both releases.
> >
> > CVS uses symbolic names (tags) to link the various RCS version numbers with a
> > global release name.
>
> The real problem doesn't really go away though. Unless I miss my guess
> (and this is surely sliding OT rapidly) you will end up with a *much*
> larger source-control database if you check revs in the wrong order ?
Yes.
Greetings,
Geert
--
Geert Uytterhoeven Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP} http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/