From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dockstar bsp
Date: Sat, 19 Jan 2013 14:32:37 +0100 [thread overview]
Message-ID: <50FAA075.80401@mind.be> (raw)
In-Reply-To: <20130117172427.190cdb5b@skate>
On 17/01/13 17:24, Thomas Petazzoni wrote:
> On Sat, 29 Dec 2012 14:45:39 -0800, Steve Calfee wrote:
[snip]
>> > board/sheevaplug/seagatedockstar/README | 62 +++++
> The README file should not be a story of how the thing was written, but
> simply how to use this configuration on this particular hardware (how
> to flash the images, etc.).
The story of how the thing was written can be part of the commit
message, however. Although 62 lines of commit message is probably too
much as well.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-01-19 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 22:45 [Buildroot] [PATCH] dockstar bsp Steve Calfee
2013-01-17 16:09 ` Steve Calfee
2013-01-17 16:24 ` Thomas Petazzoni
2013-01-17 20:02 ` Steve Calfee
2013-01-19 13:32 ` Arnout Vandecappelle [this message]
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=50FAA075.80401@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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