From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Buildroot Development <buildroot@buildroot.org>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [Buildroot] [PATCH 2/2] DEVELOPERS: Add entry for Bagas Sanjaya as Buildroot developer for git
Date: Tue, 14 Mar 2023 16:52:34 +0700 [thread overview]
Message-ID: <20230314095234.284584-3-bagasdotme@gmail.com> (raw)
In-Reply-To: <20230314095234.284584-1-bagasdotme@gmail.com>
Bagas is keen to maintain git package for Buildroot. However, due to
limited resources available, he can only do testing as far as
build testing. Other developers are needed to help him maintain the
package.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
DEVELOPERS | 3 +++
1 file changed, 3 insertions(+)
diff --git a/DEVELOPERS b/DEVELOPERS
index b49491da7a..b6d288c54f 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -273,6 +273,9 @@ F: package/orbit/
N: Attila Wagner <attila.wagner@onyxinsight.com>
F: package/python-canopen/
+N: Bagas Sanjaya <bagasdotme@gmail.com>
+F: package/git/
+
N: Bartosz Bilas <b.bilas@grinn-global.com>
F: board/stmicroelectronics/stm32mp157a-dk1/
F: configs/stm32mp157a_dk1_defconfig
--
An old man doll... just what I always wanted! - Clara
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-03-14 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 9:52 [Buildroot] [PATCH 0/2] git version bump Bagas Sanjaya
2023-03-14 9:52 ` [Buildroot] [PATCH 1/2] package/git: bump to version 2.40.0 Bagas Sanjaya
2023-03-14 22:27 ` Thomas Petazzoni via buildroot
2023-03-14 9:52 ` Bagas Sanjaya [this message]
2023-03-19 16:48 ` [Buildroot] [PATCH 2/2] DEVELOPERS: Add entry for Bagas Sanjaya as Buildroot developer for git 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=20230314095234.284584-3-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=buildroot@buildroot.org \
/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