From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ravinandan Arakali" Subject: RE: Please ignore the corrupt patches sent earlier. Date: Fri, 5 Nov 2004 16:30:33 -0800 Message-ID: <003201c4c397$d4885900$9810100a@S2IOtech.com> References: <418BE6EC.3060103@pobox.com> Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: , , , , Return-path: To: "'Jeff Garzik'" , "'koushik'" In-Reply-To: <418BE6EC.3060103@pobox.com> Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org 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. Thanks, Ravi -----Original Message----- From: Jeff Garzik [mailto:jgarzik@pobox.com] Sent: Friday, November 05, 2004 12:48 PM To: koushik 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. 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 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