From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Request to mailing list U-Boot-Users rejected
Date: Wed, 12 Dec 2007 09:15:19 -0600 [thread overview]
Message-ID: <475FFB07.5060000@freescale.com> (raw)
In-Reply-To: <20071211222611.0A360246C2@gemini.denx.de>
Wolfgang Denk wrote:
> Oh, it *is* me. As a list moderator I have to NAK these manually.
> But the way I see it I can only be fair by NAKing all such requests.
> Even if the exceed the limit by just a single byte.
This policy isn't helping anyone, however. It's making more work for you,
because you spend more time NAK'ing patches. It's more work for the people who
contribute patches, because they need to find other ways to submit the patches.
No one is saying that the limit should be removed. We're just saying that 40K
is too low. As far as I'm concerned, it has *always* been too low. 100K is
reasonable.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2007-12-12 15:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1197390201.2247.u-boot-users@lists.sourceforge.net>
2007-12-11 16:47 ` [U-Boot-Users] Request to mailing list U-Boot-Users rejected Haavard Skinnemoen
2007-12-11 19:09 ` Stefan Roese
2007-12-11 21:52 ` Timur Tabi
2007-12-11 22:13 ` Wolfgang Denk
2007-12-11 22:41 ` Mike Frysinger
2007-12-11 22:43 ` Mike Frysinger
2007-12-12 21:21 ` Jerry Van Baren
2007-12-12 0:08 ` Wolfgang Denk
2007-12-12 1:49 ` Ben Warren
2007-12-11 19:53 ` Mike Frysinger
2007-12-11 20:00 ` Scott Wood
2007-12-11 22:26 ` Wolfgang Denk
2007-12-12 9:29 ` Haavard Skinnemoen
2007-12-13 0:10 ` Wolfgang Denk
2007-12-13 6:16 ` Stefan Roese
2007-12-13 6:27 ` Kumar Gala
2007-12-13 6:31 ` ksi at koi8.net
2007-12-13 7:31 ` Robert Schwebel
2007-12-12 15:15 ` Timur Tabi [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=475FFB07.5060000@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/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