[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <804857E1F29AAC47BF68C404FC60A18465623059@ORSMSX105.amr.corp.intel.com>
Date: Fri, 6 Jun 2014 15:35:58 +0000
From: "Allan, Bruce W" <bruce.w.allan@...el.com>
To: Joe Perches <joe@...ches.com>
CC: "apw@...onical.com" <apw@...onical.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
postmaster <postmaster@...r.kernel.org>
Subject: RE: [PATCH] checkpatch: warn when patch exceeds a maximum message
size
> -----Original Message-----
> From: Joe Perches [mailto:joe@...ches.com]
> Sent: Friday, June 06, 2014 8:34 AM
> To: Allan, Bruce W
> Cc: apw@...onical.com; linux-kernel@...r.kernel.org; postmaster
> Subject: Re: [PATCH] checkpatch: warn when patch exceeds a maximum
> message size
>
> On Fri, 2014-06-06 at 08:26 -0700, Joe Perches wrote:
> > On Fri, 2014-06-06 at 15:08 +0000, Allan, Bruce W wrote:
> > > From: Joe Perches [mailto:joe@...ches.com]
> > > Sent: Thursday, June 05, 2014 6:36 PM
> > > > On Thu, 2014-06-05 at 17:00 -0700, Bruce Allan wrote:
> > > > > the maximum message size (100,000 characters) allowed by
> Majordomo at
> > > > > vger.kernel.org since that is where most Linux email lists are served.
> > > > I believe this is incorrect and the patch is unnecessary.
> > > Actually, it is correct (it even says so at
> http://vger.kernel.org/majordomo-info.html).
> > where?
>
> Duh, near the very end it does have:
>
> Message size exceeding 100 000 characters causes blocking.
>
> But I believe that info is out of date.
>
If it is out of date, can you explain how/why we got stung by it?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists