Thanks Greg.
'cvs import' does not work from within a working directory (aka
sandbox) -- i.e. it does not do anything special.
Or rather it only works by virtue of the fact that by default it'll
ignore all the administrative CVS sub-directories and the files they
contain.
Ah, the
Just a little nit:
if you end the line with a | you can drop the \
find . -name Entries | xargs grep /-kb/ \
| sed -e s|CVS/Entries:/|| -e s|/[^/]*/[^/]*/-kb/.*|| \
| xargs cvs -d $CVSROOT admin -kb
find . -name Entries | xargs grep /-kb/ |
sed -e s|CVS/Entries:/|| -e
Hi,
I'm a newcomer to CVS so please forgive me if the answer to this
question is obvious. I have tried to find an answer in the FAQs and
the Cederqvist but without success.
It seems to me that if a file is marked as binary or tagged in
CVS/Entries in a sandbox, e.g.:
/noodle.jpeg/1.1/Mon Apr 8
[ On , April 8, 2002 at 09:13:01 (-0700), Hamish Allan wrote: ]
Subject: CVS sticky information ignored on import
It seems to me that if a file is marked as binary or tagged in
CVS/Entries in a sandbox, e.g.:
/noodle.jpeg/1.1/Mon Apr 8 16:39:14 2002/-kb/TNOODLE_FINAL
when 'cvs import'ed
