On Wed, Sep 30, 2009 at 6:05 PM, Gleason, Todd <tgleason_at_impac.com> wrote:
> Thank you--that's the clearest I've seen things explained. While I
> think I understand what you've said, you won't be surprised that I don't
> like how it works in 1.5.x-1.6.x, and am glad for what 1.7 will change.
> It seems like in 1.7 we'll see all this:
> * No updating of subtree mergeinfo, removing the urge to delete subtree
Subtrees that are modified by the merge will still be updated.
> * Much higher performance when merging from the WC root (due to wc-ng
> and the subtree optimization you mentioned above), removing the urge to
> merge at the subtree level and create more subtree mergeinfo
> With all that, it sounds like the fact that Subversion doesn't identify
> that a subtree merge actually merged all the changes from a given
> revision, and elide it to a parent path, should become more or less
> irrelevant. Now I'm even more eager for 1.7 than I was before. Can you
> tell me how much of the performance improvement and subtree mergeinfo
> changes are client-side, and how much are server-side?
These are 100% client-side changes.
> if we upgrade the server to 1.6.5 now, will we have to upgrade it again
> to 1.7.x to get the desired behavior and better performance?
There are improvements to the usage of the HTTP protocol in 1.7 that
requires the server and client to both be upgraded. If you are on a
WAN or other high latency connection this will give additional
performance boost. Fairly negligible on a fast LAN though. Anyway,
that would be a reason to upgrade to 1.7 on the server. These other
changes will not require a server upgrade.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-01 00:18:26 CEST