From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] DM644x: (2nd try) This adds support for theProdrive PMDRA board, based on a DM6441
Date: Wed, 26 Mar 2008 08:34:00 +0100 [thread overview]
Message-ID: <47E9FC68.4070309@googlemail.com> (raw)
In-Reply-To: <4CD35CD1F8085945B597F80EEC8942138A24AE@exc01.bk.prodrive.nl>
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
next prev parent reply other threads:[~2008-03-26 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 11:28 [U-Boot-Users] [PATCH] DM644x: (2nd try) This adds support for theProdrive PMDRA board, based on a DM6441 Pieter Voorthuijsen
2008-03-22 13:38 ` Jean-Christophe PLAGNIOL-VILLARD
2008-03-25 9:28 ` [U-Boot-Users] [PATCH] DM644x: (2nd try) This adds support for theProdrivePMDRA " Pieter Voorthuijsen
2008-03-25 12:42 ` Wolfgang Denk
2008-03-26 0:04 ` [U-Boot-Users] [PATCH] DM644x: (2nd try) This adds support for theProdrive PMDRA " Wolfgang Denk
2008-03-26 7:18 ` Pieter Voorthuijsen
2008-03-26 7:34 ` Dirk Behme [this message]
2008-03-26 7:34 ` Wolfgang Denk
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=47E9FC68.4070309@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=u-boot@lists.denx.de \
/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.