From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Christian Couder <christian.couder@gmail.com>,
Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Hariom verma <hariom18599@gmail.com>,
Victoria Dye <vdye@github.com>
Subject: Re: Git in Outreachy? (December, 2023)
Date: Sun, 29 Oct 2023 23:53:14 +0530 [thread overview]
Message-ID: <f0378755-fd97-4624-b0c2-63844de762b9@gmail.com> (raw)
In-Reply-To: <CAP8UFD3i5ewCoaZOh09TtfuefEtWL4+z8P0_Z9DWdYCrShYheQ@mail.gmail.com>
Hi Christian and Taylor,
Excuse the huge delay in my response. I got too pre-occuppied with some
other commitments.
On 22/09/23 11:49, Christian Couder wrote:
>>
>> On Tue, Aug 29, 2023 at 10:38:45PM +0200, Christian Couder wrote:
>>> By the way, Kaartic, do you still want to be an org admin? And Taylor
>>> are you Ok with Kaartic being an org admin?
>>
>> Sorry that this dropped off of my queue. FWIW, no issues from me.
>
> Taylor, thanks for your answer!
>
> Kaartic, if you want to be org admin, just ask on the Outreachy web
> site and we will accept your request.
>
Thanks for the offer!
I think we're very close to the end of the contribution period of
Outreachy. I think the contribution period is the on that would've
needed significant participation of an Org Admin. I'm not sure if
there's anything I could contribute to much in coming days. If there's
anything I could help with, kindly let me know. I'll be glad to help :-)
--
Sivaraam
prev parent reply other threads:[~2023-10-29 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 1:07 Git in Outreachy? (December, 2023) Taylor Blau
2023-08-18 15:10 ` Christian Couder
2023-08-18 15:17 ` Taylor Blau
2023-08-22 6:14 ` Kaartic Sivaraam
2023-08-23 18:40 ` Taylor Blau
2023-08-29 17:44 ` Kaartic Sivaraam
2023-08-29 17:54 ` Taylor Blau
2023-08-29 20:38 ` Christian Couder
2023-09-02 6:06 ` Kaartic Sivaraam
2023-09-21 20:46 ` Taylor Blau
2023-09-22 6:19 ` Christian Couder
2023-10-29 18:23 ` Kaartic Sivaraam [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=f0378755-fd97-4624-b0c2-63844de762b9@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=me@ttaylorr.com \
--cc=vdye@github.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).