netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ravinandan Arakali" <ravinandan.arakali@s2io.com>
To: "'Jeff Garzik'" <jgarzik@pobox.com>
Cc: "'koushik'" <raghavendra.koushik@s2io.com>,
	<romieu@fr.zoreil.com>, <netdev@oss.sgi.com>,
	<leonid.grossman@s2io.com>, <rapuru.sriram@s2io.com>,
	<alicia.pena@s2io.com>
Subject: RE: Please ignore the corrupt patches sent earlier.
Date: Mon, 8 Nov 2004 11:07:56 -0800	[thread overview]
Message-ID: <001f01c4c5c6$422f5050$9810100a@S2IOtech.com> (raw)
In-Reply-To: 

Jeff,
By default, sendmail puts the From: address as "root@linux.site".
We suspect this may be causing your pobox domain to reject the
message. We'll try sending the first patch to you with
From: address set to Koushik's(using -f option of sendmail).
Kindly ack if you get the patch and we'll send the rest of the
patches.

Thanks,
Ravi

-----Original Message-----
From: Ravinandan Arakali [mailto:ravinandan.arakali@s2io.com]
Sent: Monday, November 08, 2004 9:56 AM
To: 'Jeff Garzik'
Cc: 'koushik'; 'romieu@fr.zoreil.com'; 'netdev@oss.sgi.com';
'leonid.grossman@s2io.com'; 'rapuru.sriram@s2io.com';
'alicia.pena@s2io.com'
Subject: RE: Please ignore the corrupt patches sent earlier.


Jeff,
All the 12 patches were sent by Koushik on Fri evening. We(Rapuru,
myself) have received it.
mailq shows the following error for your address "Sender address
rejected: Domain not found". Is there an alternate address where
we can send the patches ?

Can anybody on the netdev list confirm if they got the patches ?

Regards,
Ravi

-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Saturday, November 06, 2004 9:11 AM
To: ravinandan.arakali@s2io.com
Cc: 'koushik'; romieu@fr.zoreil.com; netdev@oss.sgi.com;
leonid.grossman@s2io.com; rapuru.sriram@s2io.com; alicia.pena@s2io.com
Subject: Re: Please ignore the corrupt patches sent earlier.


Ravinandan Arakali wrote:
> Jeff,
> Thanks for the excellent suggestion. We have used this method to send all
> the 12 patches. Note that since our mail server went down and came back
> up during this process, the mail containing patch3 has appeared twice. 
> Pls ignore the duplicate.

Alas, I'm still waiting for the patches...  Does 'mailq' show messages 
waiting to be delivered?

	Jeff

             reply	other threads:[~2004-11-08 19:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 19:07 Ravinandan Arakali [this message]
2004-11-08 22:58 ` Please ignore the corrupt patches sent earlier Jeff Garzik
2004-11-08 23:24   ` Ravinandan Arakali
  -- strict thread matches above, loose matches on Subject: below --
2004-11-05 13:23 koushik
2004-11-05 20:47 ` Jeff Garzik
2004-11-06  0:30   ` Ravinandan Arakali
2004-11-06 17:10     ` Jeff Garzik
2004-11-08 17:55       ` Ravinandan Arakali
2004-11-08 11:57   ` David Woodhouse

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='001f01c4c5c6$422f5050$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 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).