info-cvs
[Top][All Lists]
Advanced

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

Re: Q on mulitple users in same directory...


From: Mark E. Hamilton
Subject: Re: Q on mulitple users in same directory...
Date: Thu, 22 Jun 2006 15:14:13 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.7.12) Gecko/20050920

jsWalter wrote:
On Thu, June 22, 2006 2:32 pm, Larry Jones wrote:

jsWalter writes:

Is there a way that this will not always ask for Daves password, but
ask for mine?

Check out your own copy of the project instead of screwing up Dave's.



Well, thank you Larry, for that wonderful piece of enlightenment.

I'll try this again.

This is on the testing server.

The sandbox Dave created is not "Daves". It sits on the test server and
any 1 of 3 of us can update files on tht server.

We do *not* develop on that server, just test.

Just want to be able to have any one of us UPDATE files there. We don't
commit from there.

Just some ideas of of the top of my head:

1. Try using 'cvs -d :ext:address@hidden:/cvs update ...' when you want to update. According to the manual '-d takes precedence over CVS/Root.

http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_2.html#SEC11

2. Export your testing sandbox directory rather than checkout/update. You'll have to export everything each time, instead of doing an update, but you won't have those pesky CVS/Root files hanging around.

3. Try using an alias that does this from your sandbox directory:

find . -name 'Root' -exec sed -i -e "s/ext:.*@/ext:walter@/" {} \;

Then do your 'cvs update'.

--
----------------
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
505-844-7666





reply via email to

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