[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(no subject)

From: root
Subject: (no subject)
Date: Mon, 13 Aug 2001 05:10:52 -0400

>From address@hidden  Thu Feb  8 11:10:44 2001
>Return-Path: <address@hidden>
Received: from (address@hidden [])
        by (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
        for <address@hidden>; Thu, 8 Feb 2001 11:10:39 +0900
Received: from localhost ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14QgNU-0007he-00; Wed, 07 Feb 2001 21:00:08 -0500
Received: from ([])
        by with smtp (Exim 3.16 #1 (Debian))
        id 14QgLe-0007es-00
        for <address@hidden>; Wed, 07 Feb 2001 20:58:14 -0500
Received: (qmail 8844 invoked from network); 8 Feb 2001 01:58:13 -0000
Received: from (HELO 
  by with SMTP; 8 Feb 2001 01:58:13 -0000
Received: by (8.10.0) id f181wBP08651; Wed, 7 Feb 2001 
17:58:11 -0800
From: Mike Castle <address@hidden>
To: "'address@hidden'" <address@hidden>
Subject: Re: Multiple Repositories on a server
Message-ID: <address@hidden>
Reply-To: Mike Castle <address@hidden>
Mail-Followup-To: Mike Castle <address@hidden>,
        "'address@hidden'" <address@hidden>
References: <address@hidden>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <address@hidden>; from address@hidden on Thu, Feb 08, 2001 at 
11:46:54AM +1100
Sender: address@hidden
Errors-To: address@hidden
X-BeenThere: address@hidden
X-Mailman-Version: 2.0
Precedence: bulk
List-Help: <mailto:address@hidden>
List-Post: <mailto:address@hidden>
List-Subscribe: <>,
List-Id: Announcements and discussions for the CVS version control system 
List-Unsubscribe: <>,
List-Archive: <>
Date: Wed, 7 Feb 2001 17:58:11 -0800
Status: O
Content-Length: 1570
Lines: 40

On Thu, Feb 08, 2001 at 11:46:54AM +1100, Ajay Gopinath wrote:
> Hi,
> We are in the process of implementing CVS on Linux and there is a
> requirement for creating two repositories on the server.
> Please can you let me know how to go about it.

Use different definitions for the -d option, and simply init them.

cvs -d /path/to/first/repository init
cvs -d /path/to/second/repository init

Then just have your users use the appropriate path when checking out the
code from the server:

cvs -d :ext:server:/path/to/first/respository co foo
cvs -d :ext:server:/path/to/second/respository co bar

>From that point on, you generally don't have to worry about the cvsroot
options because they're encoded in the files in the CVS subdirectories.
Generally referring, of course, to common commands like update, commit,
tag, and so on.  Commands that don't work against an existing checked out
area (export, checkout, rlog, rtag) will need the appropriate -d option.

In this set up, it might be wise to not set a CVSROOT environment variable,
but instead, always explicitly use the -d so you don't accidently try to
act upon the wrong repository.

       Mike Castle       Life is like a clock:  You can work constantly
  address@hidden  and be right all the time, or not work at all and be right at least twice a day.  -- mrc
    We are all of us living in the shadow of Manhattan.  -- Watchmen

Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]