All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Jan-Bernd Themann <ossthema@de.ibm.com>
Cc: netdev <netdev@vger.kernel.org>,
	meder@de.ibm.com, raisch@de.ibm.com, schickhj@de.ibm.com,
	themann@de.ibm.com, tklein <osstklei@de.ibm.com>
Subject: Re: EHEA: Is there a size limit below 80K for patches?
Date: Thu, 08 Jun 2006 07:34:36 -0400	[thread overview]
Message-ID: <44880B4C.3020403@garzik.org> (raw)
In-Reply-To: <4487FB64.1070307@de.ibm.com>

Jan-Bernd Themann wrote:
> Hello,
> 
> we tried two times to send a patch set. In both cases the second 
> (largest) patch
> got lost. The first one was a bit above 100k, the second one we tried 
> was like 75K.
> 
> Any idea what might be the problem?

It might be size, or tripping a spam filter.

For a new driver, do the sane thing and just post a URL.

	Jeff




  reply	other threads:[~2006-06-08 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 10:26 EHEA: Is there a size limit below 80K for patches? Jan-Bernd Themann
2006-06-08 11:34 ` Jeff Garzik [this message]
2006-06-08 12:17   ` Christoph Raisch
2006-06-08 14:48     ` Jeff Garzik

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=44880B4C.3020403@garzik.org \
    --to=jeff@garzik.org \
    --cc=meder@de.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=ossthema@de.ibm.com \
    --cc=osstklei@de.ibm.com \
    --cc=raisch@de.ibm.com \
    --cc=schickhj@de.ibm.com \
    --cc=themann@de.ibm.com \
    /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.