[PLUG] CVS questions concerning ntop...

Steve Bonds 1s7k8uhcd001 at sneakemail.com
Mon Sep 20 16:44:02 PDT 2004


On 20 Sep 2004 16:04:23 -0700, Darkhorse plug_0-at-robinson-west.com wrote:

You might want to review any of these fine manuals on CVS:
  + https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs.html
  + https://www.cvshome.org/new_users.html
  + https://www.cvshome.org/docs/blandy.html

> I have a copy checked out.  If I want to update my copy of the
> source code, can I update over a copy I've already
> checked out?

Yep.  See https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_16.html#SEC154

> Can I use my local copy as a CVS repository and check out a
> copy from there 

No, you can't.

> or do I need to hand import the source code I've checked out into my own
> local CVS server?

Yes, this is how you would do it.

See https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_13.html#SEC103
for more detail.

> Can one CVS repository update a second one?

No.

> With this model, how do changes in the a local CVS repository
> work back up to a remote one?

You have to send a patch to someone with write access to the CVS
repository.  Once they validate that the patch is valid and useful,
they will put it in.

> What if the remote CVS repository isn't under my control?

See above.  The developers serve as gatekeepers to ensure that the
code that goes into the CVS repository is consistent with the code
standards for the project.

> I've noticed a directory called CVS in the source code.  What
> are these special directories a CVS checkout creates for?

They hold metadata that describe the files in your CVS working area
(what you checked out).  They're all text files, take a look at them
and their contents should be pretty obvious.  (versions, dates,
locations of repositories/modules, etc.)

  -- Steve




More information about the PLUG mailing list