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: Fri, 15 Apr 2022 10:53:19 +0530 [thread overview]
Message-ID: <20220415052319.49380-1-chakrabortyabhradeep79@gmail.com> (raw)
In-Reply-To: <0179a76a-182a-0501-a4ae-800ddb53b8cd@gmail.com>
Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:
> Rather than deciding the plan in haste, I would recommend that you put
> some more thought into deciding the plan for your proposal. Take some
> time to reflect on the different parts required for the project,
> potential things that might interfere with the project etc. This would
> help you come up with a more refined plan.
>
> This might need some deeper understanding of the project that you would
> be working on. Do feel to ask us in case you face any issues with this.
>
> Also, you could use Taylor's suggestion as a possible starting point for
> the plan:
>
> > If you end up working on this, I would suggest budgeting a week or so
> > to try out a couple of different sub-projects, and then decide where
> > to spend your time from there.
Got it! thanks! Will do as you suggested.
Thanks :)
next prev parent reply other threads:[~2022-04-15 5:23 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
2022-04-14 20:29 ` Kaartic Sivaraam
2022-04-15 5:23 ` Abhradeep Chakraborty [this message]
-- 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=20220415052319.49380-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).