public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: David Gibson <hermes@gibson.dropbear.id.au>,
	jt@hpl.hp.com,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Dan Williams <dcbw@redhat.com>, Pavel Roskin <proski@gnu.org>
Subject: Re: [PATCH] Update in-kernel orinoco drivers to upstream current CVS
Date: Thu, 08 Jul 2004 19:30:55 -0400	[thread overview]
Message-ID: <40EDD92F.50001@pobox.com> (raw)
In-Reply-To: <20040709011750.A12605@electric-eye.fr.zoreil.com>

Francois Romieu wrote:
> Dumb question: how should the patches be published once they start to be
> ready for wider review ?


Individual emails or foo.tar.bz2, I would think...

	Jeff



  reply	other threads:[~2004-07-08 23:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02 22:26 [PATCH] Update in-kernel orinoco drivers to upstream current CVS Jean Tourrilhes
2004-07-02 23:07 ` Francois Romieu
2004-07-03 20:15   ` Francois Romieu
2004-07-03 23:11   ` Francois Romieu
2004-07-04  2:13   ` David Gibson
2004-07-04 17:17     ` Francois Romieu
2004-07-05 23:14       ` Francois Romieu
2004-07-05 23:39         ` Jeff Garzik
2004-07-06 22:54           ` Francois Romieu
2004-07-07  1:25             ` Michael Clark
2004-07-07 18:50               ` Pavel Roskin
2004-07-08 22:04                 ` Jeff Garzik
2004-07-09 18:53                   ` [PATCH] Updated pci-skeleton.c Pavel Roskin
2004-07-09 19:18                     ` Jeff Garzik
2004-07-08 23:17             ` [PATCH] Update in-kernel orinoco drivers to upstream current CVS Francois Romieu
2004-07-08 23:30               ` Jeff Garzik [this message]
2004-07-03  6:08 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2004-07-02 19:11 Dan Williams
2004-07-02 19:25 ` Jeff Garzik
2004-07-04  2:01   ` David Gibson

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=40EDD92F.50001@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=dcbw@redhat.com \
    --cc=hermes@gibson.dropbear.id.au \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=romieu@fr.zoreil.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