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

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Jim Meyering <jim@...>
Cc: git list <git@...>, Paul Eggert <eggert@...>
Date: Friday, August 15, 2008 - 2:28 pm

Jim Meyering <jim@meyering.net> writes:


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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] add boolean diff.suppress-blank-empty config opt..., Junio C Hamano, (Fri Aug 15, 2:28 pm)