From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 22 Feb 2003 16:35:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 22 Feb 2003 16:35:41 -0500 Received: from havoc.daloft.com ([64.213.145.173]:33218 "EHLO havoc.gtf.org") by vger.kernel.org with ESMTP id ; Sat, 22 Feb 2003 16:35:40 -0500 Date: Sat, 22 Feb 2003 16:45:45 -0500 From: Jeff Garzik To: David Dillow Cc: "David S. Miller" , linux-kernel@vger.kernel.org Subject: Re: typhoon rx_copybreak Message-ID: <20030222214545.GE27739@gtf.org> References: <20030222.004504.113090900.davem@redhat.com> <3E57D54A.5FCDD811@thedillows.org> <20030222214128.GC27739@gtf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030222214128.GC27739@gtf.org> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.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