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

RE: Recurse into same-repos externals at commit time.

From: Bert Huijben <bert_at_qqmail.nl>
Date: Mon, 29 Aug 2011 23:52:09 +0200

> -----Original Message-----
> From: Neels J Hofmeyr [mailto:neels_at_elego.de]
> Sent: maandag 29 augustus 2011 20:47
> To: dev_at_subversion.apache.org
> Subject: Re: Recurse into same-repos externals at commit time.
>
> On 08/29/2011 06:23 PM, C. Michael Pilato wrote:
> > On 08/29/2011 12:15 PM, Neels J Hofmeyr wrote:
> >> - when an external is passed as explicit target, still require
> >> --include-externals?
> >
> > No. Because we've recommended in the issue I referenced exactly this
> > behavior as a workaround for this missing feature.
> >> I'd say yes (thinking of 'svn commit *')
> > Is 'svn commit *' really something that people do? I mean, commit is
> > recursive by nature, so I'd suspect that 'svn commit' is the more common
> > invocation.
> [...]
> > When explicitly named, though, we've
> > always allowed such commits because from the perspective of such an
> > operation, we're not looking at an external, just a working copy. (An
> > external's external-ness is defined outside it's own scope, right?)
>
> This is a good point, but IMHO ceases to be one with release 1.7. There no
> longer is a detached administrative .svn/ inside an external dir. It really
> is an external inside a "real" WC, always detectable, always overlayed.

There still is a .svn in a directory external in 1.7.

        Bert
Received on 2011-08-29 23:52:37 CEST

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