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

Re: ill-logic of externals handing with explicit --revision

From: Fabien COELHO <fabien_at_coelho.net>
Date: Wed, 1 Oct 2008 16:51:20 +0200 (CEST)

Dear Karl,

>> It seems that svn (including 1.5) does not propagate explicit
>> command-line --revision when following svn:external links. Although it
>> makes sense for distinct repositories, or when explicit revisions are
>> required in the external link, but there are two cases where a
>> different behavior would help:
>> - if the external link is directly in the *same* repository
>> - if the --revision is a date (-r {2008-01-01}).
>> [...]
> Meaning it should be forwarded whenever the svn:external line in
> question does not already have a -r option?
> That is: whenever an explicit revision is passed to a checkout or
> update, any svn:externals should also be checked out or updated using
> the same revision number *unless* they already have an explicitly
> specified revision of their own.

Yes, if it is in the *same* repository where the revision number makes

The current status is that when checking out at a revision,
"svn:externals"-linked subprojects are extracted at the latest revision

> (This is separate from supporting -r{DATE} syntax in svn:externals. In
> fact, I'm kind of surprised we don't already. Are you sure we don't --
> have you tried it?)


svn pset svn:externals 'foo -r {2007-01-01} http://foo' .
svn: Invalid revision number found parsing '{2007-01-01}'

svn pset svn:externals 'foo -r{2007-01-01} http://foo' .
svn: Invalid revision number found parsing '{2007-01-01}'

But maybe I got the syntax wrong?

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-01 16:51:58 CEST

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