From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Pedro Aguilar <paguilar@paguilar.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] DEVELOPERS: Add packages guile and bdwgc to Pedro Aguilar
Date: Sun, 6 Feb 2022 11:54:09 +0100 [thread overview]
Message-ID: <20220206115409.1f1174ee@windsurf> (raw)
In-Reply-To: <20220206092048.1901703-1-paguilar@paguilar.org>
On Sun, 6 Feb 2022 10:20:48 +0100
Pedro Aguilar <paguilar@paguilar.org> wrote:
> Signed-off-by: Pedro Aguilar <paguilar@paguilar.org>
> ---
> DEVELOPERS | 2 ++
> 1 file changed, 2 insertions(+)
Applied to master after fixing the patch to sort package entries
alphabetically. Thanks a lot for volunteering to look after those
packages!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-06 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 9:20 [Buildroot] [PATCH v1] DEVELOPERS: Add packages guile and bdwgc to Pedro Aguilar Pedro Aguilar
2022-02-06 10:54 ` Thomas Petazzoni via buildroot [this message]
2022-02-17 13:53 ` 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=20220206115409.1f1174ee@windsurf \
--to=buildroot@buildroot.org \
--cc=paguilar@paguilar.org \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox