Re: svn use case question

Hi,

David Waite <mass@akuma.org> writes:
> Just a $0.02 on this subject - my ideal 'import' would actually just
> be a svn add which did not require a root wc. it would schedule the
> whole imported tree for addition, and perhaps would scan for things
> such as mime-type and line endings and set those properties, but
> wouldn't affect the repository until I did a commit. This would allow
> me to have much stronger control over my imports, and would leave me
> after import with a valid working copy.
>
> -David Waite

wouldn't this sequence do:

<create new repository>

cd /my/to/be/imported/tree
svn co <repository-URL> .
svn add *
svn -m 'Initial source import' commit

IMHO, this should just do what you wanted - it adds all the files in the
source directory to your repository, and leaves a functional wc.

I just tested it to make sure:

  536 svnadmin create ../testw.repo
  537 svn co file:///home/joe/Projects/xmlrw/testw.repo .
  538 ls -la
  539 svn add *
  540 -m 'Initial source import' commit

Greetings,
        Joerg

-- 
Leading SW developer  - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org