Date: Wed, 14 Feb 2001 02:06:12 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Kent Hauser <kent@tfd.com> Cc: questions@freebsd.org Subject: Re: mechanics of cvs committing Message-ID: <20010214020611.A66720@mollari.cthul.hu> In-Reply-To: <200102140836.f1E8ar671536@chapel-hill.tfd.com>; from kent@tfd.com on Wed, Feb 14, 2001 at 03:36:53AM -0500 References: <200102140836.f1E8ar671536@chapel-hill.tfd.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 14, 2001 at 03:36:53AM -0500, Kent Hauser wrote: >=20 > I ask because my company uses CVS to develop code at multiple > sites (in multiple countries), and the commits are painful. > Currently, at irregular intervals, we rdist local code back > to the main repository & do a local commit. And then rdist out > the new cvsroot -- as cvsup is written in modula or pascal or something > that I've not been able to get to compile on our SunOS 4.1.4 > root server. >=20 > How is it done in the FreeBSD world? Assuming IP connectivity & > permissions, what's the magic? We use SSH to allow committers to remotely commit from their local checked out source trees. For example, I have the following alias: rcvs env CVS_RSH=3Dssh cvs -d kris@freefall.freebsd.org:/home/ncvs For more information on what makes it all work, take a look in /home/ncvs/CVSROOT for the various support scripts and so on. Kris --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6iliTWry0BWjoQKURArZ2AJ9vKNoiN5wHE5m7cXfwu/QGfKVPqgCeI7LK e2ssRBo7Bi+h+T3bJci08KI= =2uc+ -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010214020611.A66720>