mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Allan, Bruce W" <bruce.w.allan@intel.com>
Cc: "apw@canonical.com" <apw@canonical.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	postmaster <postmaster@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: warn when patch exceeds a maximum message size
Date: Fri, 06 Jun 2014 08:34:02 -0700	[thread overview]
Message-ID: <1402068842.12513.7.camel@joe-AO725> (raw)
In-Reply-To: <1402068405.12513.5.camel@joe-AO725>

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@perches.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.



  reply	other threads:[~2014-06-06 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  0:00 Bruce Allan
2014-06-06  1:35 ` Joe Perches
2014-06-06 15:08   ` Allan, Bruce W
2014-06-06 15:26     ` Joe Perches
2014-06-06 15:34       ` Joe Perches [this message]
2014-06-06 15:35         ` Allan, Bruce W
2014-06-06 15:45           ` Joe Perches
2014-06-06 15:51             ` Allan, Bruce W
2014-06-06 15:35       ` Allan, Bruce W

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=1402068842.12513.7.camel@joe-AO725 \
    --to=joe@perches.com \
    --cc=apw@canonical.com \
    --cc=bruce.w.allan@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=postmaster@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®