From: Auke Kok <auke-jan.h.kok@intel.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
sam@ravnborg.org, mec@shout.net, bunk@stusta.de,
linux-kernel@vger.kernel.org
Subject: Re: Linguistic fixes for Documentation/kbuild/
Date: Fri, 28 Jul 2006 10:45:02 -0700 [thread overview]
Message-ID: <44CA4D1E.9040203@intel.com> (raw)
In-Reply-To: <20060728103756.9f2d8507.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> On Thu, 27 Jul 2006 22:14:29 +0200 (MEST) Jan Engelhardt wrote:
>> I have done a look-through through Documentation/kbuild/ and my corrections
>> (proposed) are attached. It is bzipped because the uncompressed diff is
>> 41KB and may have get stuck on the magic list limit (30 or 40, I believe 40).
>
> or 80 or 100 KB ? Certainly more than 40 KB.
From "http://vger.kernel.org/majordomo-info.html":
"Message size exceeding 100 000 characters causes blocking."
So that's 97KB :)
Cheers,
Auke
prev parent reply other threads:[~2006-07-28 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 20:14 Linguistic fixes for Documentation/kbuild/ Jan Engelhardt
2006-07-27 21:01 ` Sam Ravnborg
2006-07-28 17:37 ` Randy.Dunlap
2006-07-28 17:45 ` Auke Kok [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=44CA4D1E.9040203@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=bunk@stusta.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
--cc=rdunlap@xenotime.net \
--cc=sam@ravnborg.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