> -----Original Message-----
> From: Markus Schaber [mailto:m.scha...@3s-software.com]
> Sent: dinsdag 2 augustus 2011 10:27
> To: André Hänsel; users@subversion.apache.org
> Subject: AW: Do svn:externals changes need to be committed to work?
>
> Hi, André,
>
> Von: André Hänsel [mailto:an...@webkr.de]
> > I am trying to add an svn:externals definition to a working copy. I set
> > the property on a directory and ran svn update on that directory, but
> > nothing is fetched.
> >
> > I found this article:
> > http://blogs.gnome.org/johannes/2008/02/20/svnexternals-for-noobs/
> > However, from other documentation it's unclear to me if a commit is
really
> > necessary for svn:external to work. Of course, I don't want to commit an
> > untested external definition.
> >
> > I am using TortoiseSVN 1.6.15 built with Subversion 1.6.16.
>
> From my experience with Subversion 1.6, the directory needs to be
> committed, but not the svn:external definition itsself.
>
> So maybe you can commit the empty directory, and then add the externals
> properties and test them before committing them.
In Subversion 1.7 externals definitions don't have to be committed to work
correctly. In 1.6 I would recommend committing them before applying, but in
many cases it will work if you don't do that.
We integrated the tracking of which externals a working copy has in the new
working copy store. The next 'svn update' will apply the changes even if the
directory on which they are defined was never committed.
Bert
