Re: importing a module b/w two repositories

[Eric Siegerman]

On Fri, Sep 14, 2001 at 05:00:14PM +0500, Muhammad Shakeel wrote:
> How to import a module from one repository A of CVS to our another cvs
> repository B with all previous version control information.

The only way I know of is to just move the ,v files from one repo
to the other.  This might make sense in some circumstances, as
part of a reorganization for example, but NOT for your purposes.

(Digression:  Even in circumstances where this did make sense,
there would be issues having to do with getting back old
(pre-reorg) versions.  It'd probably safer to *copy* the files to
the new repo, and keep the old repo as a historical archive,
being sure to make it read-only (via chmod, burning to CD, or
whatever) to avoid accidental commits to the no-longer-active
repository.)

> Basically i am trying to make a Main cvs  repository for Release manager
> and others repositories for the each development group.

Just don't.

> Problem is how
> to synchronize the other individual group repositories with the main
> release manager repository.

Yes, that is the problem.  CVS has no support for synchronizing
between repositories, so whatever help you want with
synchronization, you'd have to invent yourself, or find as a
third-party addon.  (CVSup -- http://www.polstra.com/projects/freeware/CVSup/
-- might be of help; I don't know for sure, having never used it
myself).

But CVS has a mechanism for synchronizing multiple streams of
development within *one* repository, so why not use that and save
yourself a lot of grief?  I refer to branches of course.

        http://www.cvshome.org/docs/manual/cvs_5.html#SEC54

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea.
        - RFC 1925 (quoting an unnamed source)