From: Maxim Grigoriev <maxim@tensilica.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about Buildroot concepts and strategies
Date: Fri, 06 Mar 2009 11:45:40 -0800 [thread overview]
Message-ID: <49B17D64.50707@hq.tensilica.com> (raw)
Hello Peter and BUILDROOT maintainers,
I understand you are busy individuals, and I'm sorry
for bothering you. An excuse could be I'm trying to
understand what BUILDROOT project is all about. Is it
similar to other open source projects or somewhat different ?
Are BUILDROOT maintainers interested in adding new
architectures to the project ?
On March 3d, I tried to start submitting Xtensa BUILDROOT :
http://lists.busybox.net/pipermail/buildroot/2009-March/026260.html
follow-ups :
http://lists.busybox.net/pipermail/buildroot/2009-March/026263.html
http://lists.busybox.net/pipermail/buildroot/2009-March/026289.html
Tensilica is eager to become a part of BUILDROOT.
We made a commitment to support Xtensa BUILDROOT
and try to do our best to improve generic BUILDROOT.
Does BUILDROOT project has a concept of architecture
maintainers ? I mean developers with write-access,
who can check in architecture-specific updates without
approval and commit generic updates after approval from
main maintainers.
Thanks,
-- Maxim
next reply other threads:[~2009-03-06 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 19:45 Maxim Grigoriev [this message]
2009-03-07 5:58 ` [Buildroot] Question about Buildroot concepts and strategies Marc Gauthier
2009-03-08 3:02 ` Thiago A. Corrêa
2009-03-09 22:15 ` Maxim Grigoriev
2009-03-09 20:09 ` Peter Korsgaard
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=49B17D64.50707@hq.tensilica.com \
--to=maxim@tensilica.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