Hyrum K. Wright wrote:
> Vlad Georgescu wrote:
>> The old code used the revision specified by -r as both a peg rev and an
>> op rev, but now svn_opt_resolve_revisions will set the peg rev to HEAD
>> for all existing externals definitions, which I think is a
>> backward-incompatible change.
> That is correct. There is precedent for doing this, though. We made
> the same change when adding peg revision syntax to commands, such as
> 'svn copy' and 'svn log'.
This line of thought feels incomplete to me.
Yes, users can change their behaviors at the command-line to take advantage
of (or otherwise deal with) a new syntax. But they *can't* easily modify
their version history and tweak old svn:externals values such that they
continue to work after an upgrade of their Subversion client. Then again,
one could argue that they'd have equal trouble retroactively fixing
versioned build scripts and such that made use of the pre-peg-rev
Is this an apples-to-apples comparison, or is there passion fruit in our midst?
C. Michael Pilato <email@example.com>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Tue Feb 20 22:38:08 2007