After skimming this blog, it appears that the extra svn:merginfo on
unrelated subtrees will be fixed in 1.7. If that is correct, then I will
simply wait patiently for 1.7.
http://blogs.open.collab.net/svn/2009/11/where-did-that-mergeinfo-come-from.html
Thanks again,
Phillip
On Fri, Feb 5, 2010 at 1:01 PM, Phillip Hellewell <sshock_at_gmail.com> wrote:
> At my company we are using SVN 1.6.4 (server) and a variety of clients
> (SmartSVN, Tortoise, command-line).
>
> At first we wanted to keep things simple and just always do merges at the
> root level (e.g., in c:\branch run "svn merge -c 12345
> https://host/svn/trunk").
>
> Unfortunately, merging was taking a considerable amount of time (up to
> several minutes), so we started doing merges at lower subdirectory levels
> (e.g., in c:\branch\subdir1\subdir2 running "svn merge -c 12345
> https://host/svn/trunk/subdir1/subdir2).
>
> Unfortunately now the svn:mergeinfo properties have started showing up all
> over the place. That's not a problem in itself, but when we do a merge it
> updates every subdir / subfile that has a svn:mergeinfo property.
> Personally I think SVN ought to update only subdirs that are related to the
> change (e.g., ancestors of changed files). Not only would that keep the
> svn:megeinfo from propagating all over, but it would speed up merges.
>
> Is this something that is on the horizon to be fixed, or am I missing
> something? I'm not subscribed to the list, so please CC me on any response.
>
> Thanks,
> Phillip
>
Received on 2010-02-05 21:20:51 CET