From: "Ravinandan Arakali" <ravinandan.arakali@s2io.com>
To: "'Jeff Garzik'" <jgarzik@pobox.com>
Cc: "'Francois Romieu'" <romieu@fr.zoreil.com>, <netdev@oss.sgi.com>,
<leonid.grossman@s2io.com>, <raghavendra.koushik@s2io.com>,
<rapuru.sriram@s2io.com>, <alicia.pena@s2io.com>
Subject: RE: [PATCH 2.6.9-rc2 1/12] S2io: cosmetic changes
Date: Thu, 28 Oct 2004 18:10:59 -0700 [thread overview]
Message-ID: <005301c4bd54$26daea00$9810100a@S2IOtech.com> (raw)
In-Reply-To: <418181D9.5010603@pobox.com>
Jeff,
Looks like outlook client is garbling some of the patch.
We'll try to send using different client, but can you pls
try with -l option on all the patches and see if it applies
cleanly ?
Thanks for your patience.
Ravi
-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Thursday, October 28, 2004 4:34 PM
To: ravinandan.arakali@s2io.com
Cc: 'Francois Romieu'; netdev@oss.sgi.com; leonid.grossman@s2io.com;
raghavendra.koushik@s2io.com; rapuru.sriram@s2io.com;
alicia.pena@s2io.com
Subject: Re: [PATCH 2.6.9-rc2 1/12] S2io: cosmetic changes
With this new resend, I tried with both my automated scripts, and
applying manually as well.
All attempts succeed on patches #1 and #2, but fail on #3 - #12.
If I manually add the "-l" argument to patch(1), then patch #3 succeeds.
That implies that somewhere in your process, whitespace in your
patches is getting corrupted.
Jeff
next prev parent reply other threads:[~2004-10-29 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 22:50 [PATCH 2.6.9-rc2 1/12] S2io: cosmetic changes Ravinandan Arakali
2004-10-28 23:33 ` Jeff Garzik
2004-10-29 1:10 ` Ravinandan Arakali [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-28 18:33 Ravinandan Arakali
2004-10-28 18:48 ` Jeff Garzik
2004-10-28 19:06 ` Jeff Garzik
2004-10-28 22:01 ` Ravinandan Arakali
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='005301c4bd54$26daea00$9810100a@S2IOtech.com' \
--to=ravinandan.arakali@s2io.com \
--cc=alicia.pena@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.