Thread
-
Re: [HACKERS] CVSup
Maurice Gittens <mgittens@gits.nl> — 1998-05-01T11:46:01Z
-----Original Message----- From: The Hermit Hacker <scrappy@hub.org> To: Maurice Gittens <mgittens@gits.nl> Cc: hackers@postgreSQL.org <hackers@postgreSQL.org> Date: vrijdag 1 mei 1998 19:34 Subject: Re: [HACKERS] CVSup > > If you remove the 'tag=.' part of the CVSup config file, you can >pull down the complete CVS repository to your machine to manipulate as you >want to... > What way would suggest to keep in sync with the changes other folks are making? I mean, if I have the repository on my local system I still have to get changes changes merged in from the "main" postgresql repository. When I think about it all solutions seem more clumsy (and less flexible) than simply using the standard remote access to the repository. Could you enlighten me? With thanks from Maurice.
-
Re: [HACKERS] CVSup
Marc G. Fournier <scrappy@hub.org> — 1998-05-01T11:54:24Z
On Fri, 1 May 1998, Maurice Gittens wrote: > > -----Original Message----- > From: The Hermit Hacker <scrappy@hub.org> > To: Maurice Gittens <mgittens@gits.nl> > Cc: hackers@postgreSQL.org <hackers@postgreSQL.org> > Date: vrijdag 1 mei 1998 19:34 > Subject: Re: [HACKERS] CVSup > > > > > > If you remove the 'tag=.' part of the CVSup config file, you can > >pull down the complete CVS repository to your machine to manipulate as you > >want to... > > > > What way would suggest to keep in sync with the changes other folks are > making? I mean, if I have the repository on my local system I still have to > get changes changes merged in from the "main" postgresql repository. > When I think about it all solutions seem more clumsy (and less flexible) > than simply using the standard remote access to the repository. > > Could you enlighten me? If you pull down the repository using CVSup into /usr/local/cvsroot, for example, and set your CVSROOT environment variable to point to that, you access the same thing that everyone with commit privileges has access to, except you don't have commit privileges... In one sense, this is better...you don't have to deal with the lag of connecting to the remove CVS server every time you want to look at a log or a diff...the only time you have to "re-sync" with the remote server is when you want to pull down any recent changes, which, if you follow the committers mailing list, you do when you notice a rash of changes... A dialup PPP user is better served by pulling own theh whole CVS repositiry and then being able to disconnect/work then using CVS directly where you need to be connected to do anything...
-
Re: [HACKERS] CVSup
Kent S. Gordon <kgor@inetspace.com> — 1998-05-01T13:16:36Z
>>>>> "mgittens" == Maurice Gittens <mgittens@gits.nl> writes: > -----Original Message----- From: The Hermit Hacker > <scrappy@hub.org> To: Maurice Gittens <mgittens@gits.nl> Cc: > hackers@postgreSQL.org <hackers@postgreSQL.org> Date: vrijdag 1 > mei 1998 19:34 Subject: Re: [HACKERS] CVSup >> If you remove the 'tag=.' part of the CVSup config file, you >> can pull down the complete CVS repository to your machine to >> manipulate as you want to... >> > What way would suggest to keep in sync with the changes other > folks are making? I mean, if I have the repository on my local > system I still have to get changes changes merged in from the > "main" postgresql repository. When I think about it all > solutions seem more clumsy (and less flexible) than simply using > the standard remote access to the repository. 1) Remote CVS is a resource pig, especially for large tree. It puts a large load on the server. I would guess the load is easily 10x larger for remote CVS vs CVSUP. cvs log/diff being local instead of over the internet is great for development especially with dialup lines to the Internet. 2) The ability to have a local copy of the 'official tree' allows for some possible ideas to work easier. If one is making local changes the 'official tree' could be done as vendor imports into a local tree allowing local changes not to be overwritten. > Could you enlighten me? > With thanks from Maurice. -- Kent S. Gordon Architect iNetSpace Co. voice: (972)851-3494 fax:(972)702-0384 e-mail:kgor@inetspace.com -
Re: [HACKERS] CVSup
Thomas Lockhart <lockhart@alumni.caltech.edu> — 1998-05-01T13:36:47Z
> >> If you remove the 'tag=.' part of the CVSup config file, you > >> can pull down the complete CVS repository to your machine to > >> manipulate as you want to... > >> > 1) Remote CVS is a resource pig, especially for large tree. It puts a > large load on the server. I would guess the load is easily 10x larger > for remote CVS vs CVSUP. cvs log/diff being local instead of over the > internet is great for development especially with dialup lines to the > Internet. > 2) The ability to have a local copy of the 'official tree' allows for > some possible ideas to work easier. If one is making local changes > the 'official tree' could be done as vendor imports into a local tree > allowing local changes not to be overwritten. Would someone be interested in collecting CVSup information (at least partly from the mhonarc archive)? We could/should have a chapter in the Developer's Guide on this... - Tom -
Re: [HACKERS] CVSup
Kent S. Gordon <kgor@inetspace.com> — 1998-05-01T13:47:23Z
>>>>> "lockhart" == Thomas G Lockhart <lockhart@alumni.caltech.edu> writes: > Would someone be interested in collecting CVSup information (at > least partly from the mhonarc archive)? We could/should have a > chapter in the Developer's Guide on this... I would suggest looking at the CVSup pages from FreeBSD ( http://www.freebsd.org/handbook/cvsup.html ). This page along with a similar pages for anoncvs ( http://www.freebsd.org/handbook/anoncvs.html ) are good resources for understanding the trade-offs. CVSup was developed/maintained mainly on FreeBSD ( a new release (15.4) was just announced). > - Tom -- Kent S. Gordon Architect iNetSpace Co. voice: (972)851-3494 fax:(972)702-0384 e-mail:kgor@inetspace.com