On Sat, 23 May 1998, The Hermit Hacker wrote:
> On Sat, 23 May 1998, Tom Lane wrote:
>
> > > Odd...it was doing a 'second checkout' that screwed me, where i
> > > didn't think it worked...try doing 'cvs -d <> checkout -P pgsql' and tell
> > > me what that does...
> >
> > I'd expect that to choke, because you've specified a nonexistent
> > repository...
>
> <> == :pserver:anoncvs@postgresql.org:/usr/local/cvsroot *grin*
>
> > Why would you need to do a second checkout anyway? Once you've got
> > a local copy of the CVS tree, cd'ing into it and saying "cvs update"
> > is the right way to pull an update.
>
> My understanding (and the way I've always done it) is that:
>
> cvs checkout -P pgsql
>
> Will remove any old files, update any existing, and bring in any
> new...always worked for me...
What's that? In my understanding you have to login first. Then do one
checkout. The checkout (co) creates a new directory and updates everything
at that time. If you stay in /usr/local 'co pgsql' creates
/usr/local/pgsql. Next day or week you go to /usr/local/pgsql and try
'cvs update -d'. Only the changed files will be updated on your local
disc.
-Egon
