Duncan Murdoch <murdoch <at> stats.uwo.ca> writes:
>
> Not exactly answering your question, but I wouldn't use svn import.
> Instead create an empty copy of the target directory in the repository
> (one rev) and then check it out on top of the dir you want to import,
> and add all the files. Then svn status will report on what got added
> and you can revert the additions before committing them (a second rev).
>
> This ends up with two revisions, but the files all get added in one, and
> you have a chance to fine tune the additions. It also has the side
> effect (which is usually beneficial) of leaving you with a working copy
> of the newly added directory.
>
> I suspect the fact that you can do imports this way relieves some of the
> motivation for developers to add features to svn import.
>
> Duncan Murdoch
>
I did as you suggested (found others suggesting the same approach too),
also used the --force option for good measure !
Found that I needed to add the .dir with an additional svn add,
but it all went in together with the svn commit.
Cheers,
MikeW
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 26 16:51:51 2007