|
From: | Peter S. May |
Subject: | Re: Branch mess, and starting a project with import |
Date: | Thu, 03 Jun 2004 16:12:54 -0500 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 |
Jim.Hyslop wrote:
Indeed, the CVS Book 3rd edition ( http://cvsbook.red-bean.com/ ) around page 31 outlines cvs import as the way to start a new module in the repository.Well, that is _one_ way to do it, but I really think it's a mis-use of the import command. You still have to create the entry in CVSROOT/modules (a very important step for a repository of any significant size). Haven't you ever wondered why you are *required* to provide a branch tag that will never be used?
There's nothing really to wonder about... CVS has all kinds of mechanisms that were originally designed for some other purpose than what they are normally used for now.
I think any mess produced by a *single* extra tag is negligible, and, of course, cvs import being the method suggested by both the CVS book and, in the case that it's an existing project rather than a new one, the Cederqvist as well, it's probably safe to use. It really just depends on whether it's a brand new project or one that already has files and structure.
And, of course, it's a matter of taste from there. :-) -- PSM
[Prev in Thread] | Current Thread | [Next in Thread] |