Re: [HACKERS] CVSup
От | The Hermit Hacker |
---|---|
Тема | Re: [HACKERS] CVSup |
Дата | |
Msg-id | Pine.NEB.3.95.980501075050.19987F-100000@hub.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] CVSup ("Maurice Gittens" <mgittens@gits.nl>) |
Ответы |
Re: [HACKERS] CVSup
|
Список | pgsql-hackers |
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...
В списке pgsql-hackers по дате отправления: