-u bogusfolder

Jason Rennie <[email protected]>:

>   cvs -d:pserver:[email protected]:/cvsroot login
>   cvs -d:pserver:[email protected]:/cvsroot co ifile/ifile

for the second one i used:

  cvs -d:pserver:[email protected]:/cvsroot co ifile

because this is way i'm used to.  this generates a hierarchy that
doesn't look quite right:

  0 p2 ifile-1.0.10 #lf ifile
  total 6
  1 CVS/          1 CVSROOT/      1 ifile/

normally with cvs checkout, you get one subdirectory for the module
checked out, and within this subdirectory there's just one CVS/
directory plus all the project files flat, not in an additional
subdirectory.  from then on i go to the subdirectory and update with
"cvs up".

in your setup, i'd have to cd further down into ifile to find the
normal cvs type hierarchy i recognize:  it contains the project files
and a subdirectory CVS.

> Either there's a bug in the ifile CVS setup or the commands they
> tell you to run are buggy.  Would you mind telling the Savannah
> people?  "Get Support" on the left-hand side of the any page.

but it works now!  this additional subdir is funny, though.  i went
into it, and it's business as usual.  i can "cvs update" and noone
complains.

clemens