From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: u8500 paches are being held ( was My first patch to the mailist, but being held)
Date: Wed, 23 Sep 2009 04:58:45 +0100 [thread overview]
Message-ID: <20090923035845.GF31920@trinity.fluff.org> (raw)
In-Reply-To: <747C1E83C744F44E9ACFB89FAEEC2C7B11BC3EE46D@EXDCVYMBSTM005.EQ1STM.local>
On Tue, Sep 22, 2009 at 04:05:04PM +0200, Srinidhi KASAGAR wrote:
> David,
>
> I have posted a series of patches (u8500 machine support) today and one among them was 48K which was being held by the infradead server. Do you still consider the patches of size > 40 KB are suspects? Should I need to repost the whole patch series by splitting it to match 'your 40K' limit OR is there any possibility that the patch get posted to the list?
>
> git format-patch -M did not help either.
I've always felt that patches that big are probably too big to review
properly anyway. But that's just my personal view on the matter.
PS, word-wrap your postings to under 77 characters per line.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2009-09-23 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 14:05 u8500 paches are being held ( was My first patch to the mailist, but being held) Srinidhi KASAGAR
2009-09-23 3:58 ` Ben Dooks [this message]
2009-09-23 7:17 ` Pavel Machek
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=20090923035845.GF31920@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.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 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.