In
this case, I'd import a blank project, and then use "cvs add" in a script to add
the
files,
using the -kb option accordingly. Here's a
c-shell pseudo-code
#
Assume *.h and *.cpp files are text files, and the rest are binary
files...
for f
in `find .`; then
if [ -f $f ];
then
# found a
file, test if binary
if [ $f ==
*.h || $f == *.cpp ]; then
# add binary file
cvs add -kb $f;
else
# add text file
cvs
add $f;
else
if [ -d $f ];
then
# add directory
cvs add $f;
fi;
fi;
done
You get the idea. Gurus may have a better
solution though....
-chris
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bret A Cooper
Sent: Monday, June 07, 2004 4:47 PM
To: [EMAIL PROTECTED]
Subject: newbie question on initializing repository
Hello,
This is a first time user question.
We have collected all of our source files within a directory structure and are ready to initialize the cvs
repository. There are a couple thousand files. Roughly 20% are binary type files and are scattered
around throughout various directories.
My original plan was to run the cvs init command from the topmost directory and be done. However,
I now believe its not that simple, as the binary files(only) must be initialized with the -kb option.
Is that correct? If so, any suggestions on the simplest/easiest to go about this?
Thanks,
Bret Cooper
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
