From: "Ravinandan Arakali" <ravinandan.arakali@s2io.com>
To: "'Francois Romieu'" <romieu@fr.zoreil.com>
Cc: "'Jeff Garzik'" <jgarzik@pobox.com>, <netdev@oss.sgi.com>,
<leonid.grossman@s2io.com>, <raghavendra.koushik@s2io.com>,
<rapuru.sriram@s2io.com>
Subject: RE: s2io: patch disposition
Date: Mon, 18 Oct 2004 15:38:53 -0700 [thread overview]
Message-ID: <001f01c4b563$3f6d8b70$9810100a@S2IOtech.com> (raw)
In-Reply-To: <20041018222107.GA19990@electric-eye.fr.zoreil.com>
Hi Francois,
When we resend the patches, they will be inlined in the e-mail.
Ravi
-----Original Message-----
From: Francois Romieu [mailto:romieu@fr.zoreil.com]
Sent: Monday, October 18, 2004 3:21 PM
To: Ravinandan Arakali
Cc: Jeff Garzik; netdev@oss.sgi.com; leonid.grossman@s2io.com;
raghavendra.koushik@s2io.com; rapuru.sriram@s2io.com
Subject: Re: s2io: patch disposition
Ravinandan Arakali <ravinandan.arakali@s2io.com> :
[...]
> We'll resend the original 8 patches, followed by patch to address
> your comments. Is it okay to send a single patch to address your
> comments or you want that to be split as well ?
Dumb question: is there something which prevents your patches to be
sent with an MUA which inlines patches ?
Or is there any hope for you to run some Perl crap on your computer ? :o)
--
Ueimor
prev parent reply other threads:[~2004-10-18 22:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 1:18 [PATCH 2.6.9-rc2 8/8] S2io: two buffer mode Ravinandan Arakali
2004-10-14 15:03 ` Jeff Garzik
2004-10-14 18:33 ` Raghavendra Koushik
2004-10-14 20:49 ` Chris Leech
2004-10-15 0:02 ` Raghavendra Koushik
2004-10-15 0:21 ` Leonid Grossman
2004-10-15 18:47 ` Jeff Garzik
2004-10-15 19:48 ` Leonid Grossman
2004-10-15 19:57 ` Andi Kleen
2004-10-15 23:14 ` Raghavendra Koushik
2004-10-15 23:15 ` Jeff Garzik
2004-10-14 15:05 ` s2io: patch disposition Jeff Garzik
2004-10-18 22:06 ` Ravinandan Arakali
2004-10-18 22:04 ` Jeff Garzik
2004-10-18 22:21 ` Francois Romieu
2004-10-18 22:38 ` Ravinandan Arakali [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='001f01c4b563$3f6d8b70$9810100a@S2IOtech.com' \
--to=ravinandan.arakali@s2io.com \
--cc=jgarzik@pobox.com \
--cc=leonid.grossman@s2io.com \
--cc=netdev@oss.sgi.com \
--cc=raghavendra.koushik@s2io.com \
--cc=rapuru.sriram@s2io.com \
--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;
as well as URLs for NNTP newsgroup(s).