From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NetLoop initialization bug
Date: Fri, 03 Apr 2009 13:39:37 -0700 [thread overview]
Message-ID: <49D67409.9060309@gmail.com> (raw)
In-Reply-To: <660c0f820904031320s392b010bx8796823194bcd77a@mail.gmail.com>
Hi Michael,
Michael Zaidman wrote:
> Hi Ben,
>
> On Fri, Apr 3, 2009 at 12:52 AM, Ben Warren <biggerbadderben@gmail.com> wrote:
>
>> I tried to apply it but it didn't work, but this isn't my usual computer.
>> I'll try on my other machine tonight. BTW - what mailer are you using?
>>
>>
> I used Firefox as front-end web interface to communicate with gmail
> server - the only option I have at my work place. It obviously caused
> the problem. The http://kerneltrap.org/Linux/Email_Clients_and_Patches
> perfectly describes this. Today I created the patch on my home's Linux
> with git-format-patch and sent it by git-send-email via msmtp. I would
> like to apologize for inconvenience and ask you to try patch again.
>
> BTW - what mailer do you use to communicate to the gmail server?
>
I use Thunderbird via IMAP. IMAP is nice because the messages all stay
on the server so if you have a few different machines and OSs you don't
have to worry about keeping things coherent. Sending patches through
TBird usually works, as long as you cut&paste into a 'preformat' block
(available from a pull-down menu). But it's not bulletproof. The only
sure way to send a patch without worrying about line wrapping etc. is to
use git-send-email. You can find instructions online on how to do this
with gmail, IIRC you need to have some sendmail-like relay running on
your Linux box. I don't remember the details and am not at that
computer right now.
cheers,
Ben
next prev parent reply other threads:[~2009-04-03 20:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 17:35 [U-Boot] [PATCH] NetLoop initialization bug Michael Zaidman
2009-03-27 7:59 ` Michael Zaidman
2009-03-30 5:12 ` Heiko Schocher
2009-03-30 7:45 ` Wolfgang Denk
2009-03-30 13:07 ` Michael Zaidman
2009-03-31 6:36 ` Heiko Schocher
2009-03-31 9:30 ` Detlev Zundel
2009-03-31 10:47 ` Michael Zaidman
2009-03-31 16:26 ` Michael Zaidman
2009-04-02 12:47 ` Detlev Zundel
2009-04-02 15:47 ` Michael Zaidman
2009-04-02 21:52 ` Ben Warren
2009-04-03 20:05 ` Wolfgang Denk
2009-04-03 20:20 ` Michael Zaidman
2009-04-03 20:28 ` Wolfgang Denk
2009-04-03 20:41 ` Ben Warren
2009-04-03 20:39 ` Ben Warren [this message]
2009-04-03 21:02 ` Michael Zaidman
-- strict thread matches above, loose matches on Subject: below --
2009-04-02 15:25 Michael Zaidman
2009-04-03 20:16 Michael Zaidman
2009-04-03 22:43 Michael Zaidman
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=49D67409.9060309@gmail.com \
--to=biggerbadderben@gmail.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