From: David Gibson <david@gibson.dropbear.id.au>
To: Olof Johansson <olof@lixom.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Raising list size limit
Date: Wed, 19 Dec 2007 09:33:59 +1100 [thread overview]
Message-ID: <20071218223359.GA12254@localhost.localdomain> (raw)
In-Reply-To: <20071218161208.GA7495@lixom.net>
On Tue, Dec 18, 2007 at 10:12:08AM -0600, Olof Johansson wrote:
> 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?
dtc merge was 224k, if it had stayed together with the libfdt merge it
would have been a about 300k.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-12-18 22:33 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
2007-12-18 22:33 ` David Gibson [this message]
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=20071218223359.GA12254@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.