From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] at91bootstrap: bump version to 3.2
Date: Fri, 27 Jul 2012 10:31:00 +0200 [thread overview]
Message-ID: <501251C4.1000609@mind.be> (raw)
In-Reply-To: <20120727085540.211a4709@skate>
On 07/27/12 08:55, Thomas Petazzoni wrote:
> Therefore, I'm wondering whether we should kee at91bootstrap as it is,
> and create a separate package at91bootstrap3 for the 3.x generation.
I'm not an at91 user, but this makes complete sense to me, so let's do it.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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:[~2012-07-27 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 20:31 [Buildroot] [PATCH] at91bootstrap: bump version to 3.2 spdawson at gmail.com
2012-07-26 16:35 ` Arnout Vandecappelle
2012-07-27 6:55 ` Thomas Petazzoni
2012-07-27 8:00 ` Simon Dawson
2012-07-27 8:31 ` 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=501251C4.1000609@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