[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: blame and merge tracking

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-06-08 22:06:17 CEST

Daniel Rall wrote:
> On Fri, 08 Jun 2007, Stefan Küng wrote:
>
>> Hi,
>>
>> If I understand the docs correctly here:
>> http://subversion.tigris.org/merge-tracking/func-spec.html#commutative-author-and-rev
>> the blame command will only provide the original author and revision
>> information for each line?
>
> Yes.
>
>> If it's possible, I'd like to have *all* authors and revisions reported
>> in the callback function.
>
> The API will definitely provide more information. This is already
> mentioned in the design spec (we caught this when you brought it up
> previously :)
>
> http://subversion.tigris.org/merge-tracking/design.html#audit-operations

Ah, I completely missed that one. There are just too many pages for
merge tracking :)

>> A quick scan of the blame code shows that this
>> information is available at no additional cost (as always: if I
>> understand this correctly).
>> The reason I'd like to have this information ready in the callback is
>> because my blame app (TortoiseBlame) could then show all the log
>> messages (the original and all the merging messages too) for every line.
>
> For each line, is the following sufficient?:
>
> a) The original author and revision.
> b) The merging author and revision.
>
> Or did you want something different?

Yes, that's exactly what I wanted. Thanks.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 8 22:06:33 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.