From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Shashank S <shashu8660@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
git@vger.kernel.org, Usman Akinyemi <usmanakinyemi202@gmail.com>,
Siddharth Asthana <siddharthasthana31@gmail.com>
Subject: Re: [Outreachy] Project Proposal [v3]: Implement promisor remote fetch ordering
Date: Fri, 13 Nov 2026 18:40:29 +0530 [thread overview]
Message-ID: <17a5f239-1b95-4909-b3f4-b9555039ef2e@gmail.com> (raw)
In-Reply-To: <CANHmUQQvN0xQuXqTE2imochXyQuU_ag3KHb0gkGEZ-cPLFbBYg@mail.gmail.com>
Hi Shashank,
On 11/6/26 18:48, Shashank S wrote:
>
> Design Questions and Initial Reasoning:
> -----------------------------------------------------
>
> I do not consider the design settled before mailing-list discussion. My
> initial analysis identifies the following questions.
>
> Client configuration shape:
>
> ... snip ...
>
> Server-advertised ordering
>
> ... snip ...
>
> Precedence and persistence:
>
> ... snip ...
>
> Implementation Risks:
>
> ... snip ...
>
Thank you for the additional details! It is nice to know what all you've
thought about.
> 13-Week Internship Plan:
>
> ... snip ...
This plan reads a lot better!
> Availability
>
> I can commit 40 hours per week exclusively to this project throughout
> the internship period. I have no university exams, classes, other
> jobs, or planned vacations that conflict with 7 December 2026 through
> 8 March 2027.
>
> I am based in IST (UTC+5:30) and can adjust my hours for synchronous
> discussion, pair programming, and timely mailing-list replies.
>
> Communication and Long-Term Contribution
>
> I will publish concise weekly updates covering experiments, RFC
> decisions, patches, review feedback, and next steps. I will remain
> active on the mailing list and will communicate early if a schedule or
> technical risk affects the plan.
>
> After the internship, I intend to continue contributing to Git,
> especially in promisor-remote and repository-libification work,
> including reducing remaining unnecessary reliance on global repository
> state.
>
Sounds good. Thank you for taking the time to draft this!
--
Sivaraam
prev parent reply other threads:[~2026-11-13 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 13:18 [Outreachy] Project Proposal [v3]: Implement promisor remote fetch ordering Shashank S
2026-11-13 13:10 ` 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=17a5f239-1b95-4909-b3f4-b9555039ef2e@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=shashu8660@gmail.com \
--cc=siddharthasthana31@gmail.com \
--cc=usmanakinyemi202@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