Messages in this thread | | | Subject | Re: The history of the Linux OS | Date | Tue, 24 Nov 1998 18:59:18 -0500 | From | "Brandon S. Allbery KF8NH" <> |
| |
In message <XFMail.981123191823.simon@koala.ie>, Simon Kenyon writes: +----- | On 23-Nov-98 Geert Uytterhoeven wrote: | > CVS uses symbolic names (tags) to link the various RCS version numbers with | a | > global release name. | | then i can see no good reason to stick it in cvs | if i cannot use it to track the changes to a particular FILE as the kernel mo | ved | from version to version (and to be able to ask questions like what changed in | mm.c | from 2.0.0 and 2.1.0 for example) what is the point of storing anything under | cvs +--->8
But you can. You use CVS commands to do it, and identify the file versions by their CVS tags; CVS maps the tags to the RCS revisions(*) and you get what you wanted *regardless of what RCS versions are involved*.
cvs diff -rLINUX_0_99p14 -rLINUX_2_1_129 drivers/char/console.c
is perfectly meaningful in this system and will give you the differences between the 0.99p14 and 2.1.129 versions of drivers/char/console.c. Which is the whole point of CVS.
(*) Actually, RCS does it: CVS tags are simply RCS tags which CVS keeps in sync across multiple files, since RCS doesn't have the concept of multiple related files.
If you insist on using RCS version numbers you'll have a problem anyway: in RCS you have to treat revision numbers as dotted pairs. Well, you don't absolutely *have* to, but various commands assume <branchID, revision> relationships between pairs of numbers, so "1.2.129" could not be easily represented in RCS except as 1.1.2.1.129.1. You DON'T want to go there, trust me.
-- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu carnegie mellon / electrical and computer engineering KF8NH Kiss my bits, Billy-boy.
- 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/
| |