> well, that would have been a realy nice feature 8-)
Yes, it would be :)
> I think having a list of revisions that touched a line would be a
> great improvement all on its own (perhaps as a drop down list where
> the last changed revision is shown now).
> But that information is something I would like the command line client
> to provide too ... so I try to work up the courage to ask for that
> feature in the users_at_subversion... list 8-)
Great! And don't forget to ask whether you're allowed to open an issue
for it - otherwise it will get forgotten.
> By the way, is the blame info computed client- or server-side?
Client-Side (mostly). But blame is faster with a new server because then
the server does a lot of the diffing so the client doesn't have to.
>> but this could cause problems with very
>> big files (we'd either have to store each revision of the file in a temp
>> file, or worse keep everything in memory). Now imagine that for files >
>> 10 MB in size...
> I'm not sure if it would be neccessary to have all revisions present
> locally. I wouldn't mind the respose time needed when the relevant
> revisions would be fetched on demand.
> The use case that triggered my original question is more of the "when
> did this line got screwed up initially" variant.
> Meanwhile I discovered 'blame previous revision' in the context menu
> of the revision/author column, that sort of does what I want.
> But I inevitably end up with multiple blame windows, that are a little
> difficult to distinguish because there is no information about the
> I think it would help if the blame window would show the blame
> revision range in the title bar.
That's a good idea!
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-11-17 18:54:18 CET