[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: Karl Fogel <kfogel_at_red-bean.com>
Date: Tue, 30 Sep 2008 21:46:24 -0400

Fabien COELHO <fabien_at_coelho.net> writes:
> 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}).
> Otherwise, the usefulness of externals to combine subprojects into one
> is greatly reduced. ISTM that explicit command-line --revision should
> be forwarded for both cases mentionned above, so as to enable to
> extract the related projects as they were at some point in time.
> Also, enabling the -r {DATE} syntax in svn:externals properties, with
> the above suggested enhancements, would also help for creating simply
> related-project multi-repository tags.

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.

(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?)

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 03:46:42 CEST

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