From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH ... resent] Atmel LCD driver GUARDTIME fix
Date: Mon, 22 Jun 2009 10:36:08 -0500 [thread overview]
Message-ID: <1245684968.13093.9.camel@localhost.localdomain> (raw)
In-Reply-To: <4A3FA3C8.3060701@mimc.co.uk>
On Mon, 2009-06-22 at 16:31 +0100, Mark Jackson wrote:
> Haavard Skinnemoen wrote:
> > Mark Jackson wrote:
> >> User-Agent: Thunderbird 2.0.0.21 (X11/20090409)
> >
> > (...)
> >
> >> My patch has been mangled ... there's an extra space at the start of each
> >> "unchanged" patch line.
> >
> > Read about how to make Thunderbird behave here:
> >
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/email-clients.txt
>
> But I've sent in patches before without any problems !!
>
> And as per my other mail on the topic, I posted to both the u-boot at denx and u-boot at avr32linux MLs, and only *one* of the incoming mails (u-boot at denx) was mangled.
>
> Any ideas ?
I'm not sure why the 2 mailing lists would behave differently, but using
"git format-patch" and "git send-email" is one way to take the email
client out of the picture. The git commands are the prefered method to
send patches, especially if you're going to be sending more in the
future.
Best,
Peter
next prev parent reply other threads:[~2009-06-22 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 14:58 [U-Boot] [PATCH ... resent] Atmel LCD driver GUARDTIME fix Mark Jackson
2009-06-22 15:01 ` Mark Jackson
2009-06-22 15:21 ` Haavard Skinnemoen
2009-06-22 15:31 ` Mark Jackson
2009-06-22 15:36 ` Peter Tyser [this message]
2009-06-22 17:29 ` Haavard Skinnemoen
2009-06-22 21:39 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-23 6:53 ` Haavard Skinnemoen
2009-06-23 7:07 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-23 7:21 ` Haavard Skinnemoen
2009-06-23 8:40 ` Jean-Christophe PLAGNIOL-VILLARD
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=1245684968.13093.9.camel@localhost.localdomain \
--to=ptyser@xes-inc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox