git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>,
	Git <git@vger.kernel.org>, Taylor Blau <me@ttaylorr.com>
Subject: Re: [GSoC][RFC][PROPOSAL] Reachability bitmap improvements
Date: Thu, 14 Apr 2022 13:50:10 +0530	[thread overview]
Message-ID: <20220414082010.14217-1-chakrabortyabhradeep79@gmail.com> (raw)
In-Reply-To: <c2190b9c-3393-730d-1bed-d793c1d32275@gmail.com>

Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:

> That's good to know. Do let us know if you have any experience with C
> and shell programming outside of your contributions to Git.

Thank you for reviewing my proposal. I used C language in my B.tech
classes. I never used C in practical/real world projects before. So,
putting altogether, no, I didn't use C and shell in real world projects
before.

> Good to see your various contributions to Git so far. Good work!

Thanks.

> s/indexes/indices/

Oops, correcting it.

> > [ ... snip ... ]
> >> ## Estimated Timeline
> >
> > [ ... snip ... ]
>
> Taylor has shared feedback on the proposal and timeline which I hope are 
> helpful to you. Specifically, Taylor said:
>
> > 
> > So I think it makes sense to try and find a way you can dip your toes
> > into 2-3 of the sub-projects and get a sense for what feels most doable
> > and interesting, then focus on that before allocating time for more
> > projects in the future.
>  >
>
> I agree with this. It's better to be practical than ambituous when 
> planning the proposal.

Okay, I am willing to work on first sub-project then. Should I remove the
other subprojects then?

> Thanks for letting us know of possible things that would interfere with 
> GSoC! Do make sure to keep us posted in case you come to know of 
> anything else.

Yes! will surely inform you in that case.

Thanks :)

  reply	other threads:[~2022-04-14  8:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 20:09 [GSoC][RFC][PROPOSAL] Reachability bitmap improvements Abhradeep Chakraborty
2022-04-13 20:03 ` Kaartic Sivaraam
2022-04-14  8:20   ` Abhradeep Chakraborty [this message]
2022-04-14 20:29     ` Kaartic Sivaraam
2022-04-15  5:23       ` Abhradeep Chakraborty
  -- strict thread matches above, loose matches on Subject: below --
2022-04-19  0:10 [GSoC][RFC][Proposal] " Plato Kiorpelidis
2022-04-06 20:46 [GSoC][RFC][PROPOSAL] " Abhradeep Chakraborty
2022-04-06 20:04 Abhradeep Chakraborty
2022-04-13 19:29 ` Taylor Blau
2022-04-14  7:58   ` Abhradeep Chakraborty
2022-04-14 14:24   ` Philip Oakley
2022-04-15  5:28     ` Abhradeep Chakraborty

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220414082010.14217-1-chakrabortyabhradeep79@gmail.com \
    --to=chakrabortyabhradeep79@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).