Lo, on Monday, February 26, Michael Thiele did write:
> Hi Richard,
>
> thank's a lot for your answer.
>
> > Check the manual; look for details on the `cvs import' command.
>
> I alread knew the import command, but I wasn't sure, whether it was
> the appropriate way.
> The disadvantage: I always have to import the entire project.
> That takes a long time on large repositories if they're remote.
Oh, sorry. I'd assumed that you wanted to add *all* of the files in this
directory structure. If that's not the case, then probably the easiest
solution would be to make a copy of the tree, remove all of the files you
don't want in CVS, and then import the copy. (Once the import is complete,
you can blow the copy away.)
> If there is only the import method to handle huge directory-trees,
> then the second question is answered as well.
> The situation is:
> - Someone adds some directories and files on the working directory.
> - He has no idea of CVS.
> - After some days he comes to me to add/commit his new/changed files
> and folders to the repository.
> - He cannot remamber which files and folders he created (sic!).
> - Now I would like to add all new files and folders (lots of them).
Yuk. That, I'm afraid, is a situation I don't really know how to handle.
Perhaps someone else on the list can contribute?
CVS import is, I think, primarily intended to integrate third-party
releases into a repository, which isn't quite what you want. You might be
able to make it work, though, but this is beyond both my experience and my
expertise.
I think you saw all of the problems with `cvs add' yourself. Far as I
know, those are the only two options.
Sorry I couldn't be more help.
Good luck,
Richard
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
