public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: David Dillow <dave@thedillows.org>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: typhoon rx_copybreak
Date: Sat, 22 Feb 2003 16:45:45 -0500	[thread overview]
Message-ID: <20030222214545.GE27739@gtf.org> (raw)
In-Reply-To: <20030222214128.GC27739@gtf.org>

On Sat, Feb 22, 2003 at 04:41:28PM -0500, Jeff Garzik wrote:
> This spams me with a lot of email, but really does optimize the
> submission process, and gets your updates into the mainline kernel very
> quickly.  Ideally, I just have to do "read, read, read, cut-n-paste your
> supplied bk pull URL"

Adding to this,
If you have a number of patches, I don't mind receiving a tarball of
patches, instead of a bunch of separate emails.  Up to you.

	Jeff




      reply	other threads:[~2003-02-22 21:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030222.004504.113090900.davem@redhat.com>
     [not found] ` <3E57D54A.5FCDD811@thedillows.org>
2003-02-22 21:41   ` typhoon rx_copybreak Jeff Garzik
2003-02-22 21:45     ` 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=20030222214545.GE27739@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=dave@thedillows.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox