Greg A. Woods writes:
>
> What I always do (and I have ~1.5GB of 3rd-party code in over 200
> modules, some very large including X11, *BSD, etc.) is keep a checked
> out working directory (or create one _before_ I begin the import) and
> then immediately after the import I do the following in that working
> directory (using your examples above):
>
> cvs update -j MAY01 -j SEP01 .
>
> and I then clean-up, check, and commit the result....
If you don't already have such a working directory for other purposes,
there's no need to create one before the import. You can just do a
checkout with merge after the fact:
cvs co -j MAY01 -j SEP01 sw
That's what I always do.
-Larry Jones
Isn't it sad how some people's grip on their lives is so precarious
that they'll embrace any preposterous delusion rather than face an
occasional bleak truth? -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
