[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Q on mulitple users in same directory...
From: |
Wiest, Damian |
Subject: |
RE: Q on mulitple users in same directory... |
Date: |
Thu, 22 Jun 2006 16:13:18 -0500 |
> -----Original Message-----
> From: jsWalter [mailto:address@hidden
> Sent: Thursday, June 22, 2006 3:35 PM
> To: address@hidden
> Subject: Re: Q on mulitple users in same directory...
>
>
> 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.
>
> I hope this helps. (I know Larry's bit of knowledge he shared
> sure did)
>
> Walter
Hey Walter,
I'm using a similar setup for a staging server. What I've done is created
an account specifically for that server and then just shared the CVS
password with everyone. You may want to lock down write permissions in the
repository so people can't commit changes as this user.
Your initial message sounded as if multiple people were using the same
working copy for development; that's a bad idea.
-Damian
==============================
Confidentiality Notice:
The content of this communication, along with any attachments, is the property
of the sender, is covered by
federal and state law governing electronic communications and may contain
confidential and legally privileged
information. If the reader of this message is not the intended recipient, you
are hereby notified that any
dissemination, distribution, use or copying of the information contained herein
is strictly prohibited. If you have
received this communication in error, please immediately contact us by email at
address@hidden, destroy
any copies or print outs of this e-mail and permanently delete the original
e-mail. Thank you