[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:20:17 -0400

>From address@hidden  Fri Feb 16 05:54:26 2001
>Return-Path: <address@hidden>
Received: from ( [])
        by (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
        for <address@hidden>; Fri, 16 Feb 2001 05:54:25 +0900
Received: from localhost ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14TVH5-0006PM-00; Thu, 15 Feb 2001 15:45:11 -0500
Received: from ([]
        by with smtp (Exim 3.16 #1 (Debian))
        id 14TVGh-0006NX-00
        for <address@hidden>; Thu, 15 Feb 2001 15:44:48 -0500
Received: (qmail 11856 invoked from network); 15 Feb 2001 20:44:42 -0000
Received: from (HELO 1gck10b) (
  by with SMTP; 15 Feb 2001 20:44:42 -0000
From: "Chris Chambers" <address@hidden>
To: "info-cvs" <address@hidden>
Subject: RE: Website development
Message-ID: <address@hidden>
MIME-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <address@hidden>
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: Thu, 15 Feb 2001 12:44:16 -0800
Status: O
Content-Length: 2125
Lines: 68

If you can't do different sandboxes for each developer, you won't be liking
concurrent source control systems. For shared resources, you need locking
version control (RCS or something).

Even with a shared "cvsdeveloper" account, you'd have issues with

I've been staring at this ugly fact for a while... if it's at all possible
to do the gruntwork required to create a sandbox for each developer, I'd
recommend going that route. Otherwise, I recommend a locking model.

> -----Original Message-----
> From: address@hidden [mailto:address@hidden Behalf Of
> Atkinson, Chip
> Sent: Thursday, February 15, 2001 12:08 PM
> To: 'address@hidden'
> Subject: Website development
> Greetings,
> I'm trying to set up CVS for a web development project and have come into
> what appears to be a minor problem and am looking for advice on
> the best way
> to fix the problem.
> We need to all work out of the same directory, which is where the
> web server
> works out of and we can't just set up multiple web servers
> because it's not
> just a regular Apache or IIS setup.
> When I check out the files for the web site they are "mine" even
> though they
> are in the common directory.  When a coworker makes changes and tries to
> commit the file, cvs needs my login and not my coworker's.  If I change
> CVS/Root to have my coworker's login, then he (or I as he) can commit the
> file in question.
> The solution to the problem that occurs to me is to give everyone the same
> login, but then that seems to get in the way of logging.  Every change is
> from somedevacct or whatever.
> Is there some other way that we can all use the same sandbox without
> resorting to a generic login?
> Here's the setup:
> CVS Server: Linux box
> CVS Clients: W-2K boxes using wincvs
> Thanks in advance,
> Chip
> _______________________________________________
> Info-cvs mailing list
> address@hidden

Info-cvs mailing list

reply via email to

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