From: Ulf Magnusson <ulfalizer.lkml@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: Why is linux-kbuild/doc dropping some of my mails?
Date: Sun, 6 Feb 2011 18:33:00 +0100 [thread overview]
Message-ID: <20110206173259.GA12461@ulf> (raw)
In-Reply-To: <20110206083512.a29f4d9c.rdunlap@xenotime.net>
On Sun, Feb 06, 2011 at 08:35:12AM -0800, Randy Dunlap wrote:
> On Sun, 6 Feb 2011 17:05:01 +0100 Ulf Magnusson wrote:
>
> > On Sun, Feb 06, 2011 at 07:57:34AM -0800, Randy Dunlap wrote:
> > > On Sun, 6 Feb 2011 16:48:32 +0100 Ulf Magnusson wrote:
> > >
> > > > linux-kbuild and linux-doc dropped both of my Kconfiglib patches, while
> > > > linux-kernel accepted them:
> > > > https://lkml.org/lkml/2011/2/1/439 (initial)
> > > > https://lkml.org/lkml/2011/2/5/174 (version 2)
> > > >
> > > > Any idea why? Looked over SubmittingPatches but couldn't find anything
> > > > obvious.
> > >
> > > AFAIK, lkml has a message size limit of 300 KB or 400 KB, while
> > > kbuild and doc have a limit of (probably) 100 KB.
> > >
> > Version 2 is only 13k though - it builds on the first one.
>
> OK, then you can try some of the Supplementary tools at
> http://vger.kernel.org/ and/or check the taboo list to see if your
> patch includes things that are not allowed:
> http://vger.kernel.org/majordomo-info.html#taboo
>
> If all else fails, you can ask <postmaster@vger.kernel.org> .
>
Never mind, it appears at http://www.spinics.net/lists/linux-kbuild/
now. Strangely, so does this thread. Maybe I just got lucky with the
timing, or the archive updates work in mysterious ways..
Excuse the spam.
/Ulf
prev parent reply other threads:[~2011-02-06 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 15:48 Why is linux-kbuild/doc dropping some of my mails? Ulf Magnusson
2011-02-06 15:57 ` Randy Dunlap
2011-02-06 16:05 ` Ulf Magnusson
2011-02-06 16:35 ` Randy Dunlap
2011-02-06 17:33 ` Ulf Magnusson [this message]
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=20110206173259.GA12461@ulf \
--to=ulfalizer.lkml@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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