Karl Fogel wrote:
> Alfred Perlstein <bright_at_mu.org> writes:
>> Thank you Karl, I guess my only concern is the upgrade path, will
>> svnmerge.py still be "sucked into" the 1.5 merge tracking system
>> once it comes out? And what about the upgrade? Just drop in new
>> binaries, dump/restore, or is it something more complex?
>
> I'm not sure I understand the question. Subversion 1.5 will be
> backwards compatible with 1.4, as per our compatibility policies, and
> regarding upgrading, see
>
> http://svn.collab.net/repos/svn/trunk/contrib/client-side/svnmerge/
>
> ...for some utilities and their documentation. Of course, by the time
> we release, everything you need to know will be written up here:
>
> http://subversion.tigris.org/svn_1.5_releasenotes.html
>
>> By the way, any idea how well svnmerge.py scales on very large repos?
>
> No, but there may be others here who do -- you might try posting that
> question as a separate thread.
svnmerge.py just wraps 'svn merge', 'svn propget' and 'svn propset' so there's
no scalability issues beyond what you would have with svn.
Regards,
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-26 00:28:05 CET