On Fri, 2002-04-26 at 14:12, Garance A Drosihn wrote:
> So, that's my pitch. I feel fairly strongly that there is a
> real advantage in following the lead of Linux (+anyone using
> gnu-diff) and NetBSD in this matter. How strongly do others
> feel that we should stick to the letter of this standard,
> because they feel the standard really has the right idea?
> And if you feel that way, then could you please explain to me
> what the advantage is? Can you come up with any tangible
> benefit of the standard which would convince a linux user to
> give up this non-standard extension which they have been
> using for at least five years?
I know that you didn't ask for it, but I'd like to voice a strong vote
of "yea" for (at least) teaching our patch to handle the "\no new line"
in diffs. I don't any more (my MB cap has been raised), but I used to
follow the wine port by rolling my own tarballs after patching with the
incremental patches that they posted on their ftp site. These were
_huge_ patch files, and almost always contained some "\no new line"
lines, that our patch would not DTRT with.
I don't care whether our diff produces those lines one way or the
other. I use vi. It doesn't believe in files without newlines at the
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-standards" in the body of the message