git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karthik Nayak <karthik.188@gmail.com>
To: "Tatarinov, Daniil" <dtatarinov3@gatech.edu>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Cc: "ps@pks.im" <ps@pks.im>,
	"shejialuo@gmail.com" <shejialuo@gmail.com>,
	 "christian.couder@gmail.com" <christian.couder@gmail.com>,
	 "shyamthakkar001@gmail.com" <shyamthakkar001@gmail.com>
Subject: Re: GSoC 2025 Proposal
Date: Fri, 4 Apr 2025 07:00:51 -0700	[thread overview]
Message-ID: <CAOLa=ZRmwSmFB1vTQ1+usMqbF0RHGF_QtboaLas6h-ZzKh34mA@mail.gmail.com> (raw)
In-Reply-To: <PH0PR07MB91768A0AE333B30ADB1D39E087A72@PH0PR07MB9176.namprd07.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

"Tatarinov, Daniil" <dtatarinov3@gatech.edu> writes:

> Hello!
>
> My name is Daniil and I am a CS freshman at Georgia Tech. I prepared the following proposal for the following project "Refactoring in order to reduce Git’s global state" that I'll attach to this email. I would like you to give me a feedback and critique on my proposal and just express your opinion if I'll be able to complete it.
>

Hello Daniil,

One of the expectations for prospective applications for the GSoC is
that they take up one of the microprojects [1] listed.

I couldn't find attached to your email, and since you've already sent in
a proposal on the list, I would also recommend that you do complete a
microproject.

Thanks,
Karthik

[1]: https://git.github.io/General-Application-Information/

> Best,
> Daniil

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 690 bytes --]

      parent reply	other threads:[~2025-04-04 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PH0PR07MB91768A0AE333B30ADB1D39E087A72@PH0PR07MB9176.namprd07.prod.outlook.com>
2025-03-26  9:34 ` GSoC 2025 Proposal Patrick Steinhardt
2025-04-04 14:00 ` Karthik Nayak [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='CAOLa=ZRmwSmFB1vTQ1+usMqbF0RHGF_QtboaLas6h-ZzKh34mA@mail.gmail.com' \
    --to=karthik.188@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=dtatarinov3@gatech.edu \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    --cc=shejialuo@gmail.com \
    --cc=shyamthakkar001@gmail.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 NNTP newsgroup(s).