This specifically covers the cases where unsafe chars occur in pathnames, and git-diff -p will escape those.From the git-diff-tree manpage:> 3. TAB, LF, double quote and backslash characters in pathnames are>    represented as \t, \n, \" and \\, respectively. If there is need>    for such substitution then the whole pathname is put in double>    quotes.This patch checks whether or not this has happened and will unescapethose paths accordingly.One thing to note here is that, depending on the position in the patchformat, those paths may be prefixed with an a/ or b/.  I've specificallymade sure to never interpret a path that actually starts with a/ or b/incorrectly.Example of that subtlety below.  Here, the actual file path is"b/normal".  On the diff file that gets encoded as "b/b/normal".     diff --git a/b/normal b/b/normal     new file mode 100644     index 0000000000000000000000000000000000000000..eaf5f7510320b6a327fb308379de2f94d8859a54     --- /dev/null     +++ b/b/normal     @@ -0,0 +1 @@     +dummy contentHere, we prefer the "---" and "+++" lines' values.  Note that thesepaths start with a/ or b/.  The only exception is the value "/dev/null",which is handled as a special case.Suppose now the file gets moved "b/moved", the output of that diff wouldthen be this:     diff --git a/b/normal b/b/moved     similarity index 100%     rename from b/normal     rename to b/movedWe prefer the "rename" lines' values in this case (the "diff" line isalways a last resort).  Take note that those lines are not prefixed witha/ or b/, but the ones in the "diff" line are (just like the ones in"---" or "+++" lines).

Specifically "string_escape" does not exist as an encoding anymore.