From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Erico Nunes <nunes.erico@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] DEVELOPERS: drop my packages
Date: Thu, 24 Oct 2024 22:42:28 +0200 [thread overview]
Message-ID: <20241024224228.55f1a784@windsurf> (raw)
In-Reply-To: <20241003152523.1131434-1-nunes.erico@gmail.com>
On Thu, 3 Oct 2024 17:25:23 +0200
Erico Nunes <nunes.erico@gmail.com> wrote:
> I still follow Buildroot development and use it for some personal
> projects, but no longer have the time to be an active contributor.
> Some of these are important defconfigs and packages to have up-to-date
> in Buildroot, and mostly other developers have been doing that work, so
> I am dropping them so that someone from the active contributors can be
> the maintainer contact for them.
>
> Signed-off-by: Erico Nunes <nunes.erico@gmail.com>
> ---
> DEVELOPERS | 12 ------------
> 1 file changed, 12 deletions(-)
Applied to master, thanks. That being said, as Arnout said: a given
package or defconfig can be associated to multiple in our DEVELOPERS
file. So if you're registered as a developer for a given package or
defconfig, it doesn't prevent anyone from being registered as a
developer for the same package or defconfig.
In any case: thanks a lot for all your contributions to Buildroot!
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:[~2024-10-24 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 15:25 [Buildroot] [PATCH] DEVELOPERS: drop my packages Erico Nunes
2024-10-05 14:32 ` Arnout Vandecappelle via buildroot
2024-10-24 20:42 ` Thomas Petazzoni via buildroot [this message]
2024-11-09 17:06 ` 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=20241024224228.55f1a784@windsurf \
--to=buildroot@buildroot.org \
--cc=nunes.erico@gmail.com \
--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 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.