netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: koushik <raghavendra.koushik@s2io.com>
Cc: romieu@fr.zoreil.com, netdev@oss.sgi.com,
	leonid.grossman@s2io.com, ravinandan.arakali@s2io.com,
	rapuru.sriram@s2io.com, alicia.pena@s2io.com
Subject: Re: Please ignore the corrupt patches sent earlier.
Date: Fri, 05 Nov 2004 15:47:40 -0500	[thread overview]
Message-ID: <418BE6EC.3060103@pobox.com> (raw)
In-Reply-To: <200411050523.49239.raghavendra.koushik@s2io.com>

koushik wrote:
> Hi All,
> 	I had sent five of my patches with the new mail client, but it seems to have introduced 
> some series of '-' charecters at the end. So please ignore all those 5 mails, I will be sending
> the series of 12 patches again (hopefully for the last time :-)).


FWIW, I have found that use of "cat email-01.txt | sendmail -t" on a 
Unix system is the easiest way to send a large number of patches.

You simply have to provide a minimal email header, a blank line, and 
then the patch content itself, in a single text file.

Example:

$ cat > email-01.txt
To: jgarzik@pobox.com
CC: netdev@oss.sgi.com
From: koushik <raghavendra.koushik@s2io.com>
Subject: [patch 2.6.10-rc1-bk14 1/12] s2io: do something

EOF

$ cat patch-description >> email-01.txt
$ cat patch >> email-01.txt
$ sendmail -t < email-01.txt

  reply	other threads:[~2004-11-05 20:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 13:23 Please ignore the corrupt patches sent earlier koushik
2004-11-05 20:47 ` Jeff Garzik [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2004-11-08 19:07 Ravinandan Arakali
2004-11-08 22:58 ` Jeff Garzik
2004-11-08 23:24   ` 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=418BE6EC.3060103@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alicia.pena@s2io.com \
    --cc=leonid.grossman@s2io.com \
    --cc=netdev@oss.sgi.com \
    --cc=raghavendra.koushik@s2io.com \
    --cc=rapuru.sriram@s2io.com \
    --cc=ravinandan.arakali@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).