From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] DEVELOPERS: add myself to toolchain topic
Date: Thu, 19 Aug 2021 00:03:56 +0200 [thread overview]
Message-ID: <20210819000356.579c339d@windsurf> (raw)
In-Reply-To: <20210818210635.352231-1-giulio.benetti@benettiengineering.com>
On Wed, 18 Aug 2021 23:06:35 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Since I've dealt and deal with toolchain bugs and their work-around very
> often add myself to toolchain topic(toolchain/).
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> V1->V2:
> * correct alphabet order
> ---
> DEVELOPERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/DEVELOPERS b/DEVELOPERS
> index af97de02de..874d47352c 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -1060,6 +1060,7 @@ F: package/nfs-utils/
> F: package/sunxi-mali-mainline/
> F: package/sunxi-mali-mainline-driver/
> F: package/udisks/
> +F: toolchain/
For internal toolchains, toolchain/ doesn't have much. It's really
package/gcc, package/binutils, package/gdb, package/glibc,
package/uclibc and package/musl that matter the most.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-18 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 21:06 [Buildroot] [PATCH v2] DEVELOPERS: add myself to toolchain topic Giulio Benetti
2021-08-18 22:03 ` Thomas Petazzoni [this message]
2021-08-18 22:23 ` Giulio Benetti
2021-08-19 13:24 ` Thomas Petazzoni
2021-08-19 14:17 ` Giulio Benetti
2021-08-19 15:41 ` [Buildroot] [PATCH v3] DEVELOPERS: add myself to toolchain topic, and to binutils and gcc packages Giulio Benetti
2021-09-06 12:28 ` 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=20210819000356.579c339d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.