AW: svn commit: r1491445 - /subversion/trunk/subversion/libsvn_fs_fs/fs_fs.c

Hi,

On Mon, Jun 10, 2013 at 01:38:48PM -0000, danielsh_at_apache.org wrote:
>> Author: danielsh
>> Date: Mon Jun 10 13:38:48 2013
>> New Revision: 1491445
>>
>> URL: http://svn.apache.org/r1491445
>> Log:
>> * subversion/libsvn_fs_fs/fs_fs.c: Restore linebreak that was removed, I suspect by accident.
>>

> It would have been easy to find what revision removed the line break if we had
> a reverse blame --- that is, a blame that walks the chain of diffs from newer
> to older, rather than from older to newer.

+1

> While we're talking about blame improvements, another one is blame a line
> range: stop as soon as every line in a given [X, Y] range is accounted for
> (use-case: svn blame | grep -5 '/line I am looking at/'). Bert says that stop
> as soon as "at least one" line in a given range would be useful for him
> (use-case: "which revision last changed [this function definition]?") and
> suggests that API users would find a callback that allows them to decide when
> to stop gathering further blame information.

Agreed.

May be this way also allows to do queries for deleted lines by making the callback stop when he finds a deleted line in a given range.

Best regards

Markus Schaber

(This email was sent from a mobile device...)

CODESYSŪ a trademark of 3S-Smart Software Solutions GmbH

Inspiring Automation Solutions
________________________________
3S-Smart Software Solutions GmbH
Dipl.-Inf. Markus Schaber | Product Development Core Technology
Memminger Str. 151 | 87439 Kempten | Germany
Tel. +49-831-54031-979 | Fax +49-831-54031-50

E-Mail: m.schaber_at_codesys.com | Web: codesys.com
CODESYS internet forum: forum.codesys.com

Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915

________________________________________
Received on 2013-06-10 16:02:02 CEST