info-cvs
[Top][All Lists]
Advanced

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

Re: A Question


From: Noel L Yap
Subject: Re: A Question
Date: Wed, 10 Jan 2001 09:41:29 -0500

Why do you have the source repository in Indian when (it sounds like) all work
is being done in the US?

If some work is being done in India, are you able to give the US developers rsh
or ssh access to the CVS server?  If not, have you looked at using pserver to
give them access?

Your process sounds broken in that, assuming work is geographically dispersed,
you chance overwriting changes -- it wouldn't matter whether you're ftp'ing or
rsync'ing or whatever.  The CVS way to get around this is to have one and only
one repository.

Noel




address@hidden on 2001.01.10 00:41:49

To:   address@hidden
cc:   (bcc: Noel L Yap)
Subject:  A Question




Hi all!

  I am new to CVS and the UNIX environment. We are currently operating from
2 locations - India and US. The latest checked out build in the US office is
ftpied to us in India. We at our end are required to put it in CVS and keep
on updating it with the new builds received.

  We have put the first build into CVS. How can we update this build with
the next one received? Do we have to first checkout the first build
somewhere at our end and then update it? Please let me know the whole
procedure for this.

  Thanks in advance.

  Manish
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.


_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs





This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co. Incorporated, its
subsidiaries and affiliates.




reply via email to

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