git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Victoria Dye <vdye@github.com>
To: Raghul Nanth A <nanth.raghul@gmail.com>, cheskaqiqi@gmail.com
Cc: derrickstolee@github.com, git@vger.kernel.org, gitster@pobox.com
Subject: Re: [GSOC] diff-index: enable sparse index
Date: Tue, 2 May 2023 10:35:57 -0700	[thread overview]
Message-ID: <522272ca-f294-b2c5-aea7-e264c9faab85@github.com> (raw)
In-Reply-To: <20230502094658.608646-1-nanth.raghul@gmail.com>

Raghul Nanth A wrote:
> Hey,
>   Thanks for the info. Your explanations make sense and I will make the
>   appropriate changes. I had two questions I had two questions regarding
>   this: 
>   I have been trying to base my changes off the 'sl/diff-files-sparse'
>   branch, but I am not sure how I would go about doing that. I thought I
>   would be just pulling changes from some remote repo but I couldn't find
>   one. So, could you let me know how I could do that?

You should be able to find that branch in the https://github.com/gitster/git
remote.

>   Also, I don't seem to have been CC'd on this email. Just wanted to point
>   that out, so that I don't accidentally miss conversations.
> 
> Thanks,
> Raghul


      reply	other threads:[~2023-05-02 17:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 19:05 [GSOC][PATCH v1] diff-index: enable diff-index Raghul Nanth A
2023-04-04  0:16 ` Junio C Hamano
2023-04-05 17:53 ` Victoria Dye
2023-04-05 19:28   ` Junio C Hamano
2023-04-08 11:23 ` [GSOC][PATCH v2] diff-index: enable sparse index Raghul Nanth A
2023-04-13 21:14   ` Victoria Dye
2023-04-19 15:15     ` RAGHUL NANTH
2023-04-22 21:25       ` Shuqi Liang
2023-05-02  9:46         ` [GSOC] " Raghul Nanth A
2023-05-02 17:35           ` Victoria Dye [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=522272ca-f294-b2c5-aea7-e264c9faab85@github.com \
    --to=vdye@github.com \
    --cc=cheskaqiqi@gmail.com \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nanth.raghul@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;
as well as URLs for NNTP newsgroup(s).