Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [uclinux-dist-devel] [Announcement] The 2012R2 buildroot Linux release for Blackfin
Date: Fri, 8 Mar 2013 17:32:21 +0100	[thread overview]
Message-ID: <20130308173221.50ef6b30@skate> (raw)
In-Reply-To: <CAAXf6LVArO=ttzj1zkz9wkxyRWkUMOU3OJQaQ0bPBykq4gt8BA@mail.gmail.com>

Dear Thomas De Schampheleire,

On Fri, 8 Mar 2013 15:52:12 +0100, Thomas De Schampheleire wrote:

> > That's also why I was proposing you to get started with all the package
> > changes first. They are a lot easier to handle, less intrusive, and
> > therefore easier to get merged.
> 
> I fully agree with Thomas P. that integrating the Blackfin changes
> into mainline buildroot would be beneficial for both the buildroot as
> the Blackfin community. As Thomas indicated, the buildroot community
> is now more alive than ever, and I'm sure that a new series of
> buildroot patches from the Blackfin community will not go unnoticed,
> especially now that you're in the middle of our radar ;-)

I agree. One example of a good thing you will benefit from being part
of the wider Buildroot community is for example our autobuilder
infrastructure. It tests which packages are building properly or not
building properly, and ultimately helps in improving Buildroot's
quality and therefore the user experience. Our autobuilders are already
regularly building Blackfin configurations.

> By the way: I don't see Sonic's replies appearing on the buildroot
> mailing list. Is it possible to keep that list in copy?

Sonic e-mails have the Buildroot list in Cc. I'm not sure why they
don't make it to the list. Probably because he is posting with his
@analog.com address, while he is subscribed with an @gmail.com address
on the Buildroot list.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-03-08 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DB904C5425BA6F4E8424B3B51A1414D173F6FB6E58@NWD2CMBX1.ad.analog.com>
2013-03-07  8:59 ` [Buildroot] [uclinux-dist-devel] [Announcement] The 2012R2 buildroot Linux release for Blackfin Thomas Petazzoni
     [not found]   ` <DB904C5425BA6F4E8424B3B51A1414D173FF40BA46@NWD2CMBX1.ad.analog.com>
2013-03-07 11:14     ` Thomas Petazzoni
     [not found]       ` <DB904C5425BA6F4E8424B3B51A1414D173FF40BDC3@NWD2CMBX1.ad.analog.com>
2013-03-08  8:33         ` Thomas Petazzoni
2013-03-08 14:52           ` Thomas De Schampheleire
2013-03-08 16:32             ` Thomas Petazzoni [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=20130308173221.50ef6b30@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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