From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dirk Behme Date: Wed, 26 Mar 2008 08:34:00 +0100 Subject: [U-Boot-Users] [PATCH] DM644x: (2nd try) This adds support for theProdrive PMDRA board, based on a DM6441 In-Reply-To: <4CD35CD1F8085945B597F80EEC8942138A24AE@exc01.bk.prodrive.nl> References: Your message of "Fri, 21 Mar 2008 12:28:49 +0100." <4CD35CD1F8085945B597F80EEC8942138A2498@exc01.bk.prodrive.nl> <20080326000414.5BE10243A7@gemini.denx.de> <4CD35CD1F8085945B597F80EEC8942138A24AE@exc01.bk.prodrive.nl> Message-ID: <47E9FC68.4070309@googlemail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Pieter Voorthuijsen wrote: >>-----Original Message----- >>From: wd at denx.de [mailto:wd at denx.de] >>In message >><4CD35CD1F8085945B597F80EEC8942138A2498@exc01.bk.prodrive.nl> >>you wrote: >> >>>2nd try, previous one was wrapped: >>>Double checked spaces and coding style... >> >>Sorry, I know this must be frustrating to you, but... > > > Yes it is.. > > >>>Content-Type: application/octet-stream; >>> >> >>name="0002-DM644x-This-adds-support-for-theProdrive-PMDRA-boar.patch" >> >>>Content-Transfer-Encoding: base64 >>>Content-Description: >>>0002-DM644x-This-adds-support-for-theProdrive-PMDRA-boar.patch >>>Content-Disposition: attachment; >>> >> >>filename="0002-DM644x-This-adds-support-for-theProdrive-PMDRA- >>boar.patch" >> >>> >>RnJvbSAzOTYyNTZiYmFkNjI2YTBhYWMzZTQ4YzhhMjVjODY1N2I0MjMyYzRkIE1vbiBTZX >> >>>AgMTcg >>> >> >>MDA6MDA6MDAgMjAwMQpGcm9tOiBQaWV0ZXIgVm9vcnRodWlqc2VuIDxwaWV0ZXIudm9vcn >> >>>RodWlq >>> >> >>c2VuQHByb2RyaXZlLm5sPgpEYXRlOiBGcmksIDIxIE1hciAyMDA4IDExOjIxOjAzICswMT >> >>>AwClN1 >>> >> >>YmplY3Q6IFtQQVRDSF0gRE02NDR4OiBUaGlzIGFkZHMgc3VwcG9ydCBmb3IgdGhlUHJvZH >> >>>JpdmUg >>> >> >>UE1EUkEgYm9hcmQsIGJhc2VkIG9uIGEgRE02NDQxCgpTaWduZWQtb2ZmLWJ5OiBQaWV0ZX >> >>>IgVm9v >> >>... >> >>Please send the patch inlune as plain text. >> >>Do NOT use base64 encoding, do not use MIME attachments. >> >>As had been mentioned a couple times before, it is strongly >>recommended that you use git-send-email to post the patches. > > > This one already got resend as plain text. I'm trying to get git-send-email to > work. Is there an easy way to test this without spamming the mailing list? First --dry-run. And if this is fine, sending them to yourself? Use your own mail address in --to instead of list address. Then, if everything is fine, add list to --too. Dirk