public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: volodya@mindspring.com, Anton Altaparmakov <aia21@cam.ac.uk>,
	John Stoffel <stoffel@casc.com>,
	CML2 <linux-kernel@vger.kernel.org>,
	kbuild-devel@lists.sourceforge.net
Subject: Re: CML2 1.3.1, aka "I stick my neck out a mile..."
Date: Mon, 30 Apr 2001 03:40:01 -0400	[thread overview]
Message-ID: <20010430034001.A5520@thyrsus.com> (raw)
In-Reply-To: <Pine.LNX.4.20.0104300303530.4671-100000@node2.localnet.net> <Pine.GSO.4.21.0104300317250.4113-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0104300317250.4113-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Mon, Apr 30, 2001 at 03:23:15AM -0400

Alexander Viro <viro@math.psu.edu>:
> >From AFW FAQ:
> 
> Q11. What is the McQuary limit?
> A11. "There once was a man from Nantucket,
>      who lost his .sig in a bucket.
>      Five lines was too long,
>      columns 80 just strong,
>      so he didn't know where to tuck it."
> A11. The limit on signature size:  "4x80".

I just added the following to the Jargon File masters:

@hd{McQuary limit} @p{} 4 lines of at most 80 characters each,
   sometimes still cited on Usenet as the maximum acceptable size of a
   @es{sig block}.  Before the great bandwidth explosion of the early
   1990s, long sigs actually cost people running Usenet servers
   significant amounts of money.  Nowadays social pressure against
   long sigs is intended to avoid waste of human attention rather
   than machine bandwidth.  Accordingly, the McQuary limit should 
   be considered a rule of thumb rather than a hard limit; it's
   best to avoid sigs that are large, repetitive, and distracting.
   See also @es{warlording}.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

What, then is law [government]? It is the collective organization of
the individual right to lawful defense."
	-- Frederic Bastiat, "The Law"

  reply	other threads:[~2001-04-30  7:39 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27 23:35 CML2 1.3.1, aka "I stick my neck out a mile..." Eric S. Raymond
2001-04-29 15:12 ` John Stoffel
2001-04-29 22:35   ` Eric S. Raymond
2001-04-29 22:43     ` [kbuild-devel] " Eric S. Raymond
2001-04-30 16:28     ` John Stoffel
2001-04-30 17:39       ` Eric S. Raymond
2001-04-30 19:16         ` Peter Samuelson
2001-04-30 19:25           ` Eric S. Raymond
2001-05-01  9:23             ` Requirement of make oldconfig [was: Re: [kbuild-devel] Re: CML2 1.3.1, aka ...] Giacomo A. Catenazzi
2001-05-01 16:31               ` Eric S. Raymond
2001-05-01 21:35                 ` Olivier Galibert
2001-05-01 22:26                   ` Tom Rini
2001-05-02 13:32           ` Giacomo Catenazzi
2001-05-02 17:49             ` Eric S. Raymond
2001-05-02 20:12               ` John Stoffel
2001-05-03  7:04                 ` Hierarchy doesn't solve the problem Eric S. Raymond
2001-05-03  7:34                   ` Urban Widmark
2001-05-03  7:46                     ` Eric S. Raymond
2001-05-03 14:33                       ` Juan Quintela
2001-05-03 16:16                         ` Eric S. Raymond
2001-05-03 22:20                       ` Mike Castle
2001-05-03 12:32                 ` Requirement of make oldconfig [was: Re: [kbuild-devel] Re: CML2 1.3.1, aka ...] Horst von Brand
2001-05-03 12:47                   ` Alan Cox
2001-05-03 13:24                     ` Horst von Brand
2001-05-03 14:40                       ` Juan Quintela
2001-05-03 16:07                       ` Eric S. Raymond
2001-05-03 16:04                   ` Eric S. Raymond
2001-05-03 17:36                     ` Alan Cox
2001-04-30  1:36   ` CML2 1.3.1, aka "I stick my neck out a mile..." Anton Altaparmakov
2001-04-30  1:41     ` Eric S. Raymond
2001-04-30  2:13       ` [kbuild-devel] " John Cowan
2001-04-30  2:24       ` Alexander Viro
2001-04-30  5:41         ` David Emory Watson
2001-04-30  5:50           ` Alexander Viro
2001-04-30  6:12             ` David Emory Watson
2001-04-30  6:53               ` Eric S. Raymond
2001-04-30  7:11                 ` [OT] " Jeff Garzik
2001-04-30  7:17                 ` Alexander Viro
2001-04-30 14:25                   ` Kai Henningsen
2001-04-30 15:54                   ` [kbuild-devel] " Eric S. Raymond
2001-04-30 10:57                 ` John Cowan
2001-04-30 13:30               ` David Woodhouse
2001-04-30 13:29             ` David Woodhouse
2001-04-30  7:05         ` volodya
2001-04-30  7:23           ` Alexander Viro
2001-04-30  7:40             ` Eric S. Raymond [this message]
2001-04-30  9:09               ` [Moving rapidly offtopic] " Henning P. Schmiedehausen
2001-04-30 16:16               ` nick
2001-04-30 17:12                 ` [kbuild-devel] " Eric S. Raymond
2001-04-30 17:20                   ` [OT] " Jeff Garzik
2001-04-30 17:25                     ` Rik van Riel
2001-04-30 19:44                   ` [kbuild-devel] " Gerhard Mack
2001-04-30 19:47                     ` nick
2001-04-30  3:26       ` volodya
2001-04-30  7:52     ` Anton Altaparmakov
2001-04-30  8:03       ` Eric S. Raymond
2001-04-30 16:17         ` volodya
2001-04-30  8:13       ` Anton Altaparmakov
     [not found] ` <15084.12830.973535.153706@gargle.gargle.HOWL>
2001-04-29 22:41   ` Eric S. Raymond

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010430034001.A5520@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=aia21@cam.ac.uk \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stoffel@casc.com \
    --cc=viro@math.psu.edu \
    --cc=volodya@mindspring.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox