git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raghul Nanth <nanth.raghul@gmail.com>
To: Victoria Dye <vdye@github.com>,
	Raghul Nanth A via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Cc: Derrick Stolee <derrickstolee@github.com>
Subject: Re: [PATCH v2] describe: enable sparse index for describe
Date: Thu, 30 Mar 2023 21:40:28 +0530	[thread overview]
Message-ID: <945ec6f2-8370-0d99-0537-a3724eefde3f@gmail.com> (raw)
In-Reply-To: <8cb2b7a2-78f2-9221-1234-62814557d2d3@github.com>



On 3/29/23 23:19, Victoria Dye wrote:
> Raghul Nanth A via GitGitGadget wrote:
>> From: Raghul Nanth A <nanth.raghul@gmail.com>
> 
> Hello! Thanks for working on this patch, it's always nice to get more sparse
> index support. Since this is your first contribution to the mailing list,
> though, it's unclear to me whether you're working on this as an independent
> contributor or if you're interested in the Google Summer of Code project
> "More Sparse Index Integrations" [1]. If you're doing this for GSoC, could
> you please prefix the title of this patch with "[GSoC]" (as noted in the
> application details [2])?
> 
> On the topic of GSoC applications - if you are submitting this for GSoC, I'm
> a bit curious as to why you jumped right into sparse index rather than first
> submitting a microproject [3]. This is a good first pass at a sparse index
> integration, but the microproject is a better way to get acquainted with the
> conventions and requirements of contributing to Git, hence the strong
> recommendation to complete one first.
> 
> [1] https://git.github.io/SoC-2023-Ideas/
> [2] https://git.github.io/General-Application-Information/
> [3] https://git.github.io/General-Microproject-Information/
> 

Hello. So, yes, I am interested in GSOC. As for the reason for choosing 
to do sparse-index, I had just missed the part about the micro-projects. 
Sorry about that. So, do I submit a micro-project patch?

And as for the changes mentioned, I will make the changes in the title

  parent reply	other threads:[~2023-03-30 16:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 14:20 [PATCH] describe: enable sparse index for describe Raghul Nanth A via GitGitGadget
2023-03-27 18:26 ` Junio C Hamano
2023-03-28 19:46   ` Derrick Stolee
2023-03-28 20:24     ` Junio C Hamano
2023-03-28 20:35       ` Derrick Stolee
2023-03-29 16:25 ` [PATCH v2] " Raghul Nanth A via GitGitGadget
2023-03-29 17:00   ` Junio C Hamano
2023-03-29 17:49   ` Victoria Dye
2023-03-29 18:27     ` Junio C Hamano
2023-03-30 16:10     ` Raghul Nanth [this message]
2023-04-03 16:37       ` Victoria Dye
2023-03-30  5:59   ` [PATCH v3] " Raghul Nanth A via GitGitGadget
2023-03-30 14:57     ` Junio C Hamano
2023-03-30 15:13       ` Junio C Hamano
2023-03-30 16:23     ` Victoria Dye
2023-03-31 15:43       ` [GSOC][PATCH] " Raghul Nanth A
2023-03-31 16:34         ` Junio C Hamano
2023-03-31 18:20     ` [GSOC][PATCH v4] " Raghul Nanth A
2023-04-03 16:34       ` Victoria Dye
2023-04-03 16:47       ` [GSOC][PATCH v5] " Raghul Nanth A
2023-04-03  7:35     ` [PATCH v4] " Raghul Nanth A

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=945ec6f2-8370-0d99-0537-a3724eefde3f@gmail.com \
    --to=nanth.raghul@gmail.com \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@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 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).