subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Phippard <markp...@gmail.com>
Subject Re: Single-commit import with properties and SVN 1.7
Date Mon, 22 Aug 2011 15:12:45 GMT
On Mon, Aug 22, 2011 at 6:00 AM, Markus Schaber
<m.schaber@3s-software.com>wrote:

> Hi,
>
> We need to add a new directory including files and properties to a
> subversion repository "in-place".
>
> With SVN 1.6, the following did work: (I know that this is only an
> artifact and was no documented / intended behavior.)
> - Checkout the parent directory to a temporary place.
> - create and svn add the data directory under the parent working copy.
> - svn add and svn propset all the children we need in the working copy.
> - svn commit the parent directory (to add everything in a single
> commit.)
> - move the data directory to the intended working copy place.
> - delete the temporary parent directory.
>
> With SVN 1.7, I only see a way to do this with 2 commits:
> - svn remote add the data directory. (First commit)
> - checkout the data directory
> - fill the data directory with contents (files and properties)
> - svn commit the data directory. (Second commit).
> (This is analogeous to the "in-place import" in the FAQ.)
>
> Is it theoretically possible with the new working copy architecture to
> allow the working copy root itself to be "scheduled for addition"?
>
>
I am confused about why the exact same sequence of commands does not work
for you with 1.7.  What does the location of the .svn folder have to do with
any of this?

The problem to me, does not seem to be the import, which you can do with one
commit just fine.  It seems to be that after it it done, you want to move
this folder somewhere else to use it?  That can be done using the detach
script to copy it to the new location:

http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/detach.py



-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

Mime
View raw message