From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Move AT91RM9200DK board support underboard/atmel
Date: Wed, 19 Mar 2008 17:29:55 +0100 [thread overview]
Message-ID: <200803191729.55577.sr@denx.de> (raw)
In-Reply-To: <20080319171901.0a8ee38e@siona.local>
On Wednesday 19 March 2008, Haavard Skinnemoen wrote:
> Good. There's an astonishing number of traps to avoid when sending
> patches via e-mail...
That's why I'm a big fan of "git-send-email". :)
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-03-19 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080316222059.A5665246C5@gemini.denx.de>
2008-03-17 11:11 ` [U-Boot-Users] [PATCH] Move AT91RM9200DK board support under board/atmel Peter Pearse
2008-03-17 11:56 ` [U-Boot-Users] [PATCH] Move AT91RM9200DK board support underboard/atmel Peter Pearse
2008-03-19 16:19 ` Haavard Skinnemoen
2008-03-19 16:29 ` Stefan Roese [this message]
2008-03-19 16:46 ` Detlev Zundel
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=200803191729.55577.sr@denx.de \
--to=sr@denx.de \
--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