From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] avr32: support and maintenance
Date: Sun, 09 Feb 2014 12:19:05 +0100 [thread overview]
Message-ID: <87fvns355i.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAHt8ZCMcprZkAp8RX7MavuZyNYcsczkFUw_tCyz4FizrRy2ieA@mail.gmail.com> (Simon Dawson's message of "Sun, 9 Feb 2014 10:58:12 +0000")
>>>>> "Simon" == Simon Dawson <spdawson@gmail.com> writes:
Hi,
> Several times over the last few years, it has been suggested that we
> drop support for the avr32 architecture in Buildroot. I have been one
> of a very small number of people who appear to still require support
> for avr32; as such, I have tried to help with maintaining the
> architecture, fixing autobuild failures etc.
> However, due to a change of job, I will no longer have time to help
> maintain the avr32 architecture support. I am wondering if there is
> anyone else on the mailing list who would be interested in helping to
> maintain avr32 support in the future?
Ok, thanks for your avr32 work and good luck with the new job!
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-02-09 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 10:58 [Buildroot] avr32: support and maintenance Simon Dawson
2014-02-09 11:19 ` Peter Korsgaard [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=87fvns355i.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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