From: Olof Johansson <olof@lixom•net>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
ppc-dev <linuxppc-dev@ozlabs•org>
Subject: Re: Raising list size limit
Date: Tue, 18 Dec 2007 10:12:08 -0600 [thread overview]
Message-ID: <20071218161208.GA7495@lixom.net> (raw)
In-Reply-To: <2420E261-C9AB-49B8-8F99-C24C7A865044@kernel.crashing.org>
On Tue, Dec 18, 2007 at 09:54:15AM -0600, Kumar Gala wrote:
>
> On Dec 18, 2007, at 6:01 AM, Josh Boyer wrote:
>
> > On Tue, 18 Dec 2007 14:36:27 +1100
> > Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> >> Hi,
> >>
> >> I am considering raising the limit on the size of postings to
> >> 400k. Does
> >> anyone have a real problem with this? Limiting message size was
> >> done to
> >> limit the damage of larges spams (and we don;t get very many of
> >> those on
> >> the list) and to ease the pain for people downloading emails over a
> >> slow
> >> (like dialup) link (and are there many of those left?).
> >
> > Fine by me!
>
> Do you really have patches that are 400k?
I'm guessing stuff such as "dtc merge" could reach those sizes?
Since it's somewhat common to cross-post patches (especially some of the
@de.ibm.com guys seem to post to 2-5 lists at a time), having a limit
higher than other lists could mean we see the same (large) patches several
times in case they bounce from other lists and get reposted. But it should
be a small fraction of the traffic no matter what.
-Olof
next prev parent reply other threads:[~2007-12-18 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 3:36 Raising list size limit Stephen Rothwell
2007-12-18 12:01 ` Josh Boyer
2007-12-18 15:54 ` Kumar Gala
2007-12-18 16:12 ` Olof Johansson [this message]
2007-12-18 22:33 ` David Gibson
2007-12-18 16:30 ` Josh Boyer
2007-12-18 23:20 ` Stephen Rothwell
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=20071218161208.GA7495@lixom.net \
--to=olof@lixom$(echo .)net \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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