[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Single-commit import with properties and SVN 1.7

From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 22 Aug 2011 11:39:34 -0400

On Mon, Aug 22, 2011 at 11:31 AM, Markus Schaber
<m.schaber_at_3s-software.com>wrote:

>
> We do not insist in the "detach" step. The "detach" step just was part of
> the workaround to get an inplace-import with SVN 1.6, just as the second
> commit is part our workaround for SVN 1.7.
>
> We need an inplace-import as we did make the decision to store object
> metadata in SVN properties. (Maybe that design decision was wrong.
> Currently, we still could change that design, as we did not release yet. All
> this is part of our mapping of the CoDeSys project database to a
> file-and-directory tree as needed by subversion.) Another reason for the
> in-place import is that it makes no sense to transfer the data over the
> network twice.
>

I am confused about what does not work with an in-place import in 1.7.

$ svnadmin create repos
$ svn co file:///`pwd`/repos wc
Checked out revision 0.
$ mkdir wc/folder
$ echo foo > wc/folder/file.txt
$ svn add wc/folder
A wc/folder
A wc/folder/file.txt
$ svn ps customprop customvalue wc/folder
property 'customprop' set on 'wc/folder'
$ svn ps customprop customvalue wc/folder/file.txt
property 'customprop' set on 'wc/folder/file.txt'
$ svn ci -m "Commit changes" wc
Adding wc/folder
Adding wc/folder/file.txt
Transmitting file data .
Committed revision 1.
$ svn pl file:///`pwd`/repos/folder
Properties on 'file:///Users/markphip/tests/repos/folder':
  customprop
$ svn pl file:///`pwd`/repos/folder/file.txt
Properties on 'file:///Users/markphip/tests/repos/folder/file.txt':
  svn:mime-type
  customprop
  svn:eol-style

What does not work that worked with 1.6?

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2011-08-22 17:40:06 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.