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

Re: Blame feature requests: view path name; deleted lines

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Tue, 28 Jun 2011 09:29:06 +0100

On 28 June 2011 06:53, Craig McQueen
<craig.mcqueen_at_beamcommunications.com> wrote:
>> -----Original Message-----
>> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
>> Sent: Monday, 27 June 2011 5:06 PM
>> To: users_at_tortoisesvn.tigris.org
>> Subject: Re: Blame feature requests: view path name; deleted lines
>>
>> On Mon, Jun 27, 2011 at 05:01, Craig McQueen
>> <craig.mcqueen_at_beamcommunications.com> wrote:
>> > Hello,
>> >
>> >
>> >
>> > Blame is a fantastic tool, very useful. I have two feature requests
>> that I
>> > would find useful, for what it’s worth:
>> >
>> >
>> >
>> > 1) Be able to view the filename/SVN path name of the file. I have
>> projects
>> > with files of the same name, which I sometimes compare. If I am not
>> paying
>> > attention, I forget which project a window belongs to, and Blame
>> doesn’t
>> > provide a way to find out. It would be good to be able to see the
>> full path
>> > in the title bar, status bar, menu item, somewhere.
>>
>> On trunk, TBlame shows the path in the window title.
>>
>> > 2) Be able to view a “blame” of when lines have been deleted. Blame
>> can show
>> > when a line has been added or modified, but not deleted. It would be
>> great
>> > to optionally show deleted lines, with strike-out or some other
>> visual
>> > indication, and with a gap in the line numbering.
>>
>> Deleted since when?
>> Imagine a file like this
>>
>> abcde
>> fghijkl
>> mnopq
>>
>> over the lifetime of the file, it gets changed to
>>
>> qponm
>> lkjihgf
>> edcba
>>
>> and then changed again and again and again and ...
>
> On further thought, maybe I understand your points. Perhaps I misunderstood you before. Is a, b, c etc meant to represent lines or characters? If lines, then I understand you're representing a file with fairly complex changes.
>
>> So which lines are deleted and should be shown? What about a line that
>> got deleted and re-added several times?
>
> I would propose showing every deletion (in the selected revision range) as a separate deletion. This is quite possible to do technically, but I agree the resulting output might become less useful for complicated change histories. This could be mitigated by:
> * TBlame allows you to select a range of revisions.
> * This feature should be optional, disabled by default, and enabled by e.g. a checkbox.
>
> In my case, I would find it quite useful for some of my files, which I had in mind when I requested this feature. E.g. "I know I deleted 3 lines in this function in the last 3 months. What revision was that in?"

The basic blame information is generated by subversion and it is what
it is. Nothing TortoiseSVN can do to change that.

The feature that you are looking for (for a line which exists in
revision N, search forward to find when that line was deleted) doesn't
exist in subversion so you would have to request it on the subversion
users list. But it does not sound like a trivial function to
implement. I'm not sure whether the proposed 'svn bisect' command
would be any help. I have not used 'git bisect' which is where the
idea derives from.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2779467
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-06-28 10:29:17 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

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