From: Derrick Stolee <derrickstolee@github.com>
To: Vivan Garg <gvivan6@gmail.com>, git@vger.kernel.org, vdye@github.com
Cc: christian.couder@gmail.com, hariom18599@gmail.com
Subject: Re: [RFC][PATCH v3] GSoC 2023 proposal: more sparse index integration
Date: Thu, 23 Mar 2023 09:38:01 -0400 [thread overview]
Message-ID: <c1ec30b8-7659-d02d-e0ac-2db424bf4feb@github.com> (raw)
In-Reply-To: <CACzddJq2USyx4ttdj9rjFJubkq-6GiEirrJJ-qym7ZmOPs+mOQ@mail.gmail.com>
On 3/23/2023 2:50 AM, Vivan Garg wrote:
> I have taken into account Victoria's suggestions and made the necessary
> changes to the previous draft. I would appreciate any feedback on the
> revised version.
>
> Additionally, I wanted to inform you that I had planned to begin working
> on git describe, but unfortunately, I broke my ankle while skiing two to
> three weeks ago. This unexpected event caused a delay in my plans.
> However, now that I have adjusted to my new lifestyle, I am confident
> that I can resume working on it.
Ouch! Hopefully things are healing well and the stress of this project
won't delay that.
Thanks,
-Stolee
next prev parent reply other threads:[~2023-03-23 13:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 8:33 [RFC][PATCH] GSoC 2023 proposal: more sparse index integration Vivan Garg
2023-02-26 9:03 ` Ashutosh Pandey
2023-02-26 23:18 ` Vivan Garg
2023-02-26 23:03 ` Victoria Dye
2023-02-26 23:52 ` Vivan Garg
2023-02-27 0:46 ` [RFC][PATCH v2] " Vivan Garg
2023-03-23 6:38 ` [RFC][PATCH v3] " Vivan Garg
2023-03-23 6:50 ` Vivan Garg
2023-03-23 13:38 ` Derrick Stolee [this message]
2023-03-28 16:20 ` Victoria Dye
2023-03-28 17:54 ` Vivan Garg
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=c1ec30b8-7659-d02d-e0ac-2db424bf4feb@github.com \
--to=derrickstolee@github.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gvivan6@gmail.com \
--cc=hariom18599@gmail.com \
--cc=vdye@github.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.