7/7/05, Lorenz <lorenznl@yahoo.com> wrote:
> > [...] In fact, a "best practice" for proper use of externals would
> > demand that all externals definitions specify a particular revision [...]
>
> perhaps attaching the actual revision of the svn:external on commit
> (only if there is not a revision attached already), while leaving the
> svn:external setting in the wc unchanged would solve the problem.
>
> When checking out a revision later you then would always get the
> svn:external@rev used a the time of the commit.
>
> Updating such a svn:external to head or any other rev would require
> to change the property first.
> What do you think?
Useful behaviour, if you are thinking along the lines that people
actually use svn:externals for what it was originally intended for.
If you look at what the poster (and mostly everyone else, I imagine?)
are using svn:externals for, it's a horrible suggestion that would
only make things worse :-).
> But for what reason someone would check out an old rev and want the
> the svn:external to be at it's head rev?
No reason - the poster describes this as a bug when creating tags.
The "bug" (?) occurs because he's using svn:externals for something
else than it was designed to do - as are the rest of us..
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 7 16:33:08 2005