Some examples: svn blame README.md
after review you run svn blame README.md -r 1:1757044 and then svn blame README.md -r 1:1757042 and so on to get back in history... nothing is lost, annotations are always there. Jacopo PS: I think there is some trick to do the same with TortoiseSVN but I can't tell you the details since I don't use it On Tue, Sep 13, 2016 at 5:16 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Le 13/09/2016 à 16:45, Jacopo Cappellato a écrit : > >> On Tue, Sep 13, 2016 at 4:36 PM, Jacques Le Roux < >> jacques.le.r...@les7arts.com> wrote: >> >> ... >>> Before applying a such change, I'd really like to know if everybody is >>> aware of what that means when it comes to svn annotations. I repeat: we >>> will then lose all the svn annotations history in all the Groovy files. >>> ... >>> >>> Jacques, are you aware that you can pass the -r argument to the >> blame/annotate command? >> >> Jacopo >> >> I must say I never use that when looking at annotations in a file in > Eclipse. It's maybe useful in certain circumstances, but I hardly see when. > And once all the lines a file has been modified in one commit, I guess -r > does not help at all, anyway you get only this information. Or do I miss > something? Should I know the revision I'm looking for? I rather try to know > when and why a line has been changed, what are the reasons of these > changes, maybe to find an related Jira, etc. > > Jacques > >
