git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] add boolean diff.suppress-blank-empty config option

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 15, 2008, 18:28 UTC
Message-ID
<7v4p5mb0a1.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<87k5eiphro.fsf@rho.meyering.net>
Jim Meyering <jim@meyering.net> 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?

Previous: Jim MeyeringNext: Jim Meyering
Message 2 of 5 in “add boolean diff.suppress-blank-empty config option”
  1. add boolean diff.suppress-blank-empty config optionJim Meyering, Aug 15, 2008
  2. Junio C HamanoAug 15, 2008
  3. Jim MeyeringAug 16, 2008
  4. Junio C HamanoAug 18, 2008
  5. add boolean diff.suppress-blank-empty config optionJim Meyering, Aug 19, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.