At 12:08 AM -0400 4/26/02, Mike Barcroft wrote:
>M. Warner Losh <firstname.lastname@example.org> writes:
> > There's lots of software (well, OK, subversion) that
> > depends on the old, historical behavior. The historical
> > behavior of diff has been to include the "this file
> > doesn't end with a newline" message, not what FreeBSD
> > hacked it to do.
>Perhaps the people working on Subversion still have time
>to fix that design before too many people start using it.
>Solaris 2.5.1, for instance, returns "Warning: missing
>newline at end of file" on stderr for this condition.
They probably will fix it, by writing their own diff and
their own patch. The same way other packages fix it,
by requiring that the user install gnu-diff & gnu-patch.
I am still wondering who it is that is better off given
the standard behavior than this particular non-standard
behavior. Not "better off" in the sense that "it is
better to follow standards", but "better off" in the
sense that it is easier to get their work done, and the
sun shines brighter, and beer tastes better -- all
because the standard does not allow patch+diff to
handle this simple case of a file which is missing the
last newline character.
but that's enough from me for tonight...
Garance Alistair Drosehn = email@example.com
Senior Systems Programmer or firstname.lastname@example.org
Rensselaer Polytechnic Institute or email@example.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-standards" in the body of the message