From: Pavel Kozlov <Pavel.Kozlov@synopsys.com>
To: Carlos O'Donell <carlos@redhat.com>,
Vineet Gupta <vineet.gupta@linux.dev>
Cc: arcml <linux-snps-arc@lists.infradead.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Pavel steping up for ARC glibc maintenance
Date: Wed, 1 Feb 2023 14:24:39 +0000 [thread overview]
Message-ID: <DM6PR12MB31463258B455490C43350D85BCD19@DM6PR12MB3146.namprd12.prod.outlook.com> (raw)
In-Reply-To: <8c92778c-edd6-12d7-848a-61dd586bd73d@redhat.com>
Hi Carlos,
Hi all,
Thanks for your greeting.
I'm glad to be here.
Can you please add me to the wiki EditorGroup?
My wiki account: PavelKozlov
I have some test results that I want to post for the coming release.
I intent to help to maintain ARC glibc port, so feel free to ask if
some code, HW verification or review will be required, all concerning ARC.
I've requested the sourceware.org account.
Looking forward to the next steps.
Thank you,
Pavel
From: Carlos O'Donell <carlos@redhat.com>
Sent: Wednesday, February 1, 2023 12:33 AM
To: Vineet Gupta <vineet.gupta@linux.dev>
Cc: arcml <linux-snps-arc@lists.infradead.org>; Pavel Kozlov <kozlov@synopsys.com>; GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Pavel steping up for ARC glibc maintenance
On 1/30/23 22:07, Vineet Gupta wrote:
> 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].
Sounds great! Welcome Pavel!
> To begin with can he be granted wiki edit access and subsequently also approve his write access to glibc sourceware repo.
We can absolutely help with the next steps.
Please follow [2] and if you get stuck anywhere just reach out on IRC or by email.
> Thx,
> -Vineet
>
>
> [1] https://urldefense.com/v3/__https://sourceware.org/glibc/wiki/MAINTAINERS*Becoming_a_maintainer_.28developer.29__;Iw!!A4F2R9G_pg!aaKwbgpslcHvrrdypX2BrPwxZt7I0x_g_mYJUHIfZhZk-D9UuJWQsmzd6SqrQWU9KTROPZ8zqEyfPU98J1EM$
> [2] https://urldefense.com/v3/__https://sourceware.org/glibc/wiki/MAINTAINERS*AccountsOnSourceware__;Iw!!A4F2R9G_pg!aaKwbgpslcHvrrdypX2BrPwxZt7I0x_g_mYJUHIfZhZk-D9UuJWQsmzd6SqrQWU9KTROPZ8zqEyfPTXW0Rz_$
>
--
Cheers,
Carlos.
prev parent reply other threads:[~2023-02-01 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 3:07 Vineet Gupta
2023-01-31 20:33 ` Carlos O'Donell
2023-02-01 14:24 ` Pavel Kozlov [this message]
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=DM6PR12MB31463258B455490C43350D85BCD19@DM6PR12MB3146.namprd12.prod.outlook.com \
--to=pavel.kozlov@synopsys.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=vineet.gupta@linux.dev \
/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).