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

AW: Do svn:externals changes need to be committed to work?

From: André Hänsel <andre_at_webkr.de>
Date: Tue, 2 Aug 2011 18:29:50 +0200

Stefan Sperling wrote:
>
> On Tue, Aug 02, 2011 at 03:54:23AM +0200, André Hänsel wrote:
> > 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.
>
> With Subversion 1.6, if you put the svn:externals property on a locally
> added directory you'll need to commit the directory before 'svn update'
> will fetch the externals.
>
> This has been fixed in Subversion 1.7, see:
> http://subversion.tigris.org/issues/show_bug.cgi?id=2267

Uh, thanks. That's it, I didn't commit the folder before creationg the
property.
Received on 2011-08-02 18:31:09 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.