"Thomas Charron" <twaffle_at_gmail.com> wrote on 05/29/2008 10:56:23 PM:
> On Thu, May 29, 2008 at 3:49 PM, <Stefan.Fuhrmann_at_etas.com> wrote:
> > "Thomas Charron" <twaffle_at_gmail.com> wrote on 05/29/2008 06:44:15 PM:
> >> Will it show these, and I've simply configured and/or done
something
> >> wrong? The trunk does have the attribute that it has had the branch
> >> merged.
> > Due to restrictions in the 1.5 API, it is hard to retrieve
> > the required information. Thus, there is no merge info in
> > the 1.5 revision graph.
>
> While albiet time consuming, you do have the information by looking
> at the svn:mergeinfo property changes in the branches and in trunk.
> This is the same information that is utilized to perform the merge
> itself. You would need to look at the branches and trunk and see when
> a property change occured on the directory. For example (these are
> completely made up logs:
>
> r66 | twaffle | 2008-05-29 08:20:17 -0400 (Thu, 29 May 2008) | 1 line
> Changed paths:
> M /branches/twaffle
>
> r57 | twaffle | 2008-05-29 08:20:17 -0400 (Thu, 29 May 2008) | 1 line
> Changed paths:
> M /trunk
>
> The modification path itself is the 'hint'. There may be a better
> way to get this information honestly, but that was my first pass
> guess. I've actually started to toss something together as a perl
> script just to see how it would work to generate a graph.
AFAIK, svn:mergeinfo can be set on *any* node, in particular on files.
Even for mid-sized repositories, there are more than 100k 'M' changes.
So, you are right that there is a formal solution but it is not
suitable for all repositories.
If the API issue should not be solved in 1.6 (or too late to be used),
I will use some heuristics similar to what you proposed.
-- Stefan^2.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-05-30 11:34:51 CEST