"C. Michael Pilato" <cmpilato@collab.net> writes:
> John Peacock <jpeacock@rowman.com> writes:
> > Ben Collins-Sussman wrote:
> > > Hm, this might be a bug. What you're saying is that 'svn up -r X'
> > > updates the working copy to revision X, but updates the externals to
> > > HEAD?
> >
> > What other choice would you have Subversion make? Externals can point
> > at a completely different repository, so there it is highly likely
> > that the same rev number has no correlation there. This could be
> > added as a FAQ item (cd into the externals directory and update to the
> > appropriate backrev if desired).
>
> Correct. In fact, a "best practice" for proper use of externals would
> demand that all externals definitions specify a particular revision so
> the a project can a) choose more intelligently when to "upgrade" to a
> newer snapshot of the external thing, and b) so that the version
> history of the main and external repositories can be more tightly
> coupled, allowing for backdates which are guaranteed to produce
> accurate results.
>
> I'll make a note to add such a thing to the Subversion book.
Couldn't the svn:externals code detect when an external subdir is from
the same repository as its parent, so that
$ svn up -rN
would update both the parent and the svn:external subdir to N in that
case? And in the not-same case, it would update the parent to N and
the external to HEAD, as it does now, of course.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 28 21:36:42 2005