Jim Meyering <jim@xxxxxxxxxxxx> writes: > GNU diff's --suppress-blank-empty option makes it so that diff does not > add a space or tab before each empty output line of context. With this > option, empty context lines are empty also in "git diff" output. AFAIK, ERN 103/120 inspired by your comment merely says an empty context is either an empty line or a line with a single space on it and does not deprecate the latter, more traditional, form (I do not know the current status of the update to the POSIX --- what's the recommended way to find it out by outsiders?) We've hacked the patch application side to accomodate this special case to grok output from recent GNU diff already. Can't we just stop at that, without having to do the same for generation side? What's the downside of not doing so? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
