Someone here suggested the same thing. At first I didn't think that it updated
the parent's CVS directory, but I was wrong. It creates the file Entries.Static
which tells CVS not to update directories that aren't already checked out.
However, the method I suggested works for files, not just directories whereas
"cvs release -d" only works on directories.
Shane
Jerry Nairn wrote:
> Thanks,
> That's pretty cool. I'm thinking of how it would be an improvement over "cvs
> release -d"ing the unwanted folders, though. Doesn't that update the
> CVS/Entries file?
> Jerry
>
> > -----Original Message-----
> > From: Shane Turner [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, May 24, 2000 5:15 AM
> > To: [EMAIL PROTECTED]
> > Subject: TIP on removing directories from working directory
> >
> >
> > I've often wanted to check out a module, then prune off the
> > directories
> > and files that
> > I didn't need. Until the other day I couldn't figure out a
> > way to do it
> > entirely with CVS commands.
> >
> > What I had been doing is deleting the directory that I didn't
> > want, then
> > manually updating the CVS/Entries file of the parent. This
> > just seemed
> > wrong.
> >
> > The other day I realized that I could use the same mechanism
> > used in the
> > suggested 'cvs ls' equivalent (cvs rdiff -s -r 0 module). I
> > could cause
> > CVS to discard the files I didn't want by specifying a non-existant
> > revision, and prune empty directories.
> >
> > cvs update -r 0 -P file-or-directory-to-remove
> >
> > Hopefully someone else will find this useful.
> >
> > Shane
> >
