From: Vineet Gupta <vineet.gupta@linux.dev>
To: Carlos O'Donell <carlos@redhat.com>
Cc: arcml <linux-snps-arc@lists.infradead.org>,
Pavel Kozlov <Pavel.Kozlov@synopsys.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Pavel steping up for ARC glibc maintenance
Date: Mon, 30 Jan 2023 19:07:10 -0800 [thread overview]
Message-ID: <323b6822-6442-0aca-15dd-3e58ed2c6953@linux.dev> (raw)
Hi Carlos,
I'd like to introduce Pavel who intends to step up to maintain ARC glibc
port and do periodic wiki updates and such.
I've pointed him to links [1] and [2].
To begin with can he be granted wiki edit access and subsequently also
approve his write access to glibc sourceware repo.
Thx,
-Vineet
[1]
https://sourceware.org/glibc/wiki/MAINTAINERS#Becoming_a_maintainer_.28developer.29
[2] https://sourceware.org/glibc/wiki/MAINTAINERS#AccountsOnSourceware
next reply other threads:[~2023-01-31 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 3:07 Vineet Gupta [this message]
2023-01-31 20:33 ` Carlos O'Donell
2023-02-01 14:24 ` Pavel Kozlov
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=323b6822-6442-0aca-15dd-3e58ed2c6953@linux.dev \
--to=vineet.gupta@linux.dev \
--cc=Pavel.Kozlov@synopsys.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).