Date: Wed, 12 Jul 2000 12:26:00 +0930 From: Greg Lehey <grog@lemis.com> To: =?iso-8859-1?Q?Wilfredo_S=E1nchez?= <wsanchez@apple.com> Cc: Bruce Evans <bde@zeta.org.au>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/make arch.c buf.c compat.c cond.c dir.c for.c hash.c job.c main.c make.c parse.c str.c suff.c targ.c util.c var.c Message-ID: <20000712122600.A30262@wantadilla.lemis.com> In-Reply-To: <200007120048.RAA09917@scv3.apple.com> References: <200007120048.RAA09917@scv3.apple.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 11 July 2000 at 17:48:34 -0700, Wilfredo Sánchez wrote: >> [Please format paragraphs with somewhat less than 520 columns.] > > I can try to wrap, but I'd have to do so by hand. But wrapping text at > the sender's end is not the right thing. Your mail client is broken, as > it should wrap for you. You might try fixing that rather than expecting > everyone to hard-wrap text for you. Some of us like letting our clients > wrap the text for us as we change the window size. This is very far from the FreeBSD guidelines, and it doesn't have much to do with the RFCs, either. RFC 822 specifies that text/plain should be displayed as sent. In addition, I can't understand why it should be an advantage to have the user wrap data without any understanding of the content. If my mail reader would perform gratuitous wrapping, your next paragraph (quoting bde) would look like this: >> Round 1: premature "long-awaited" change from $Id$ to $FreeBSD$ by >> jkh and backout of this change by peter. Affected most of the src >> tree. Round 2: (for make sources only; interleaved with round 3). >> Add $Id$. Get it wrong by duplicating $Id$, then remove one of the >> copies. Round 3: premature change from $Id$ to $FreeBSD$ by obrien >> in parts of contrib and/ir ports while core was still discussing >> the correct format for the expansion of $FreeBSD$. Fait accompli. >> Change completed by peter. End up with ugly (IMHO) formatting with >> fairly full pathname of the file in the expansion of $FreeBSD. I >> hope this round has not actually ended :-). I don't see this to be an advantage. I certainly go to a lot of trouble to format my own messages, and I wouldn't like it if some piece of marginally clever code would go and rewrap it. I don't understand why anybody would want to leave the appearance of his message to chance. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000712122600.A30262>