From: Christian Couder <christian.couder@gmail.com>
To: Jack McGuinness <jmcguinness2@ucmerced.edu>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [GSoC] Applicant Introduction, Microproject Selection
Date: Tue, 5 Apr 2022 14:01:22 +0200 [thread overview]
Message-ID: <CAP8UFD2cy++9FURkNCXFvvrP=--SXAGdV--mnXy9a09k3Mta-g@mail.gmail.com> (raw)
In-Reply-To: <BYAPR06MB4517DD6F852491B795FBC922E6E09@BYAPR06MB4517.namprd06.prod.outlook.com>
Hi Jack,
On Tue, Apr 5, 2022 at 4:33 AM Jack McGuinness
<jmcguinness2@ucmerced.edu> wrote:
>
> Hi,
>
> My name is Jack McGuinness, I'm an undergraduate at U.C. Merced, majoring in Computer Science & Engineering. I very recently found out about Google Summer of Code, and as someone who has been very interested in the concepts of open-source software for a while, I thought it would be a great opportunity to get involved and start learning more. The git-scm organization immediately stuck out to me, due to both its widespread use and my personal use. I've looked through the idea list and I plan to apply for the "Unify ref-filter formats with other pretty formats" project.
Thanks for your interest in Git and in this project!
> In preparation for this, I want to do the "Modernize a test script" microproject, but I wasn't sure if someone else was working on this already, so following the recommendation from the description, I want to instead modernize t4202. However, I want to check beforehand that someone else isn't already working on this, or if there is a better test script I could modernize.
From a quick look at the mailing list archive, it looks like no one
else is working on modernizing t4202.
Thanks,
Christian.
prev parent reply other threads:[~2022-04-05 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 21:29 [GSoC] Applicant Introduction, Microproject Selection Jack McGuinness
2022-04-05 12:01 ` Christian Couder [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='CAP8UFD2cy++9FURkNCXFvvrP=--SXAGdV--mnXy9a09k3Mta-g@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jmcguinness2@ucmerced.edu \
/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 NNTP newsgroup(s).