netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Christoph Raisch <RAISCH@de.ibm.com>
Cc: Heiko J Schick <schickhj@de.ibm.com>,
	Jan-Bernd Themann <themann@de.ibm.com>,
	Marcus Eder <meder@de.ibm.com>, netdev <netdev@vger.kernel.org>,
	ossthema@de.ibm.com, Thomas OS Klein <osstklei@de.ibm.com>
Subject: Re: EHEA: Is there a size limit below 80K for patches?
Date: Thu, 08 Jun 2006 10:48:36 -0400	[thread overview]
Message-ID: <448838C4.2050603@garzik.org> (raw)
In-Reply-To: <OF56CA8BB9.67AC7182-ONC1257187.003F6F35-C1257187.00430AFF@de.ibm.com>

Christoph Raisch wrote:
> well, now I'm confused...
> 2 People, two opinions....
> 
> 
> Here's a URL for a complete tarball, "sharing" the download location with
> our other driver.
> http://prdownloads.sourceforge.net/ibmehcad/ehea_EHEA_0002.tgz
> 
> We're waiting for a sourceforge project now since 9 days to put out a tgz,
> and it looks like many other people get upset right now by their response
> time.
> 
> So what's the "right"/preferred way to proceed?

Patches and new drivers should always go to the mailing list...... 
except for the case where they are too big to be posted to the mailing 
list.  For that special case, a URL to a patch should be posted.

	Jeff




      reply	other threads:[~2006-06-08 14:48 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
2006-06-08 12:17   ` Christoph Raisch
2006-06-08 14:48     ` Jeff Garzik [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=448838C4.2050603@garzik.org \
    --to=jeff@garzik.org \
    --cc=RAISCH@de.ibm.com \
    --cc=meder@de.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=ossthema@de.ibm.com \
    --cc=osstklei@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).