Thnx for answer. but, can not put HEAD to "from" field, because file was moved. "File not found: revision xxx, path yyy
среда, 20 марта 2024 г. в 11:19:25 UTC+4, daniel.l...@gmail.com: > It works very well for me, I'm on a Subversion 1.14.2 server (VisualSVN > server 5.3.2). Can you check the version of your SVN server? > > In the Blame dialog of TortoiseSVN you just reverse the From and To > revision fields, as in Johan's example. You can even use HEAD as the From > revision. See attached image (blame.png). > > In TortoiseBlame (see tortoiseblame.png) you will get the original text > (as in the To revision) and any deleted lines will be marked, in this case > I deleted lines 3 to 5 in revision 47. > > Kind regards, > Daniel > > > onsdag 20 mars 2024 kl. 08:12:05 UTC+1 skrev alexan...@gmail.com: > > I try run this > svn blame -r 21857:21760 debug.h > and get this answer > svn: E200007: The 'get-file-revs-reversed' feature is not supported by > 'svn://.../debug.h' > среда, 20 марта 2024 г. в 01:17:44 UTC+4, Johan Corveleyn: > > On Tue, Mar 19, 2024 at 9:26 AM Александр IY поставщик: TortoiseSVN > <torto...@googlegroups.com> wrote: > > > > Can i use tool "Blame" for search deleted blocks instead of created? And > how? > > I'm not sure whether TortoiseSVN supports this, but the core SVN > library (and commandline client) can do this as of version 1.9 (for > the client, needs at least 1.8 server). See this section from the 1.9 > release notes: > https://subversion.apache.org/docs/release-notes/1.9.html#prospective-blame > > Quoting here for convenience: > > [[[ > The blame command can now show not only when the last change to each > line of a given file was, but also when the next change will be. > > For example, to see for each line in revision 3 of README.txt what the > next revision that changed (or removed) that line would be, run svn > blame -r HEAD:3 README.txt. (You may need to pass a peg revision if > the file had been renamed since r3.) > > In the blame command, the range -r M:N always means "display > information about the file at revision N". If the range is "forward" > (M<N) then the normal blame algorithm is used, displaying for each > line in the file when it was added or last changed; if the range is > "reversed" (M>N) then the above-described sense is used, describing > for each line in rN when it was first changed (or deleted) after rN > and before rM. > > Here is an example, from Subversion's own repository. The autoconf > macro SVN_CHECK_FOR_DUNDER_BUILTINS was present in r1509167 but is not > present in HEAD. The blame command can determine the revision in which > the macro was removed: > > % svn blame -r HEAD:1509167 svn-macros.m4 > ⋮ > 1509168 danielsh AC_DEFUN([SVN_CHECK_FOR_DUNDER_BUILTINS], > ]]] > > -- > Johan > > -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/ae36bcf4-cf96-4264-ac0d-587c3308df77n%40googlegroups.com.
