From: Shuqi Liang <cheskaqiqi@gmail.com>
To: Christian Couder <christian.couder@gmail.com>,
git@vger.kernel.org, Victoria Dye <vdye@github.com>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Hariom verma <hariom18599@gmail.com>,
nasamuffin@google.com
Subject: Re: Projects for the next Outreachy round
Date: Tue, 26 Sep 2023 23:30:30 -0400 [thread overview]
Message-ID: <CAMO4yUEws6CmBH+rYynnGGsX067iJRgyQwVxa2b4mkYwnV_u+A@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD1bsez-eMis5yH7Esds+LkhMnj0qTUMFPL1tRuDv2fiPw@mail.gmail.com>
On Tue, Sep 26, 2023 at 10:48 AM Christian Couder
<christian.couder@gmail.com> wrote:
>
> So Shuqi and Kousik, please tell us if you would like to continue
> working on your projects or if it's Ok if we propose them for
> Outreachy.
Hi Christian,
I'm afraid I won't have sufficient time to take on the remaining
commands in the upcoming school year. I'd like to leave those for other
contributors who are interested.
>It would be nice though if I got an idea about what
> should be done next and how much work is left in general in this area.
> (Shuqi's GSoC final report at
> https://cheskaqiqi.github.io/2023/08/22/Final/ doesn't talk much about
> this.) Perhaps even if Shuqi is continuing to work on the project,
> there is still work that could be done in parallel on other commands
> than the ones he is working on.
Sorry for not providing more details in my final report. In 2023 ideas[1]
git write-tree, git diff-files, git diff-tree, git worktree have all
been successfully
implemented with sparse index integration.There are some remaining
issues in git check-attr related to diffs.[2][3]
Two other commands on the list are being worked on by Raghul:
'git describe' has been successfully integrated, 'git diff-index'
still need more work. The remaining commands on the list have not been
started on.
[1]https://git.github.io/SoC-2023-Ideas/
[2]https://lore.kernel.org/git/20230811142211.4547-3-cheskaqiqi@gmail.com/
[3]https://cheskaqiqi.github.io/2023/08/20/Week9-10/
hope that helps!
Shuqi
next prev parent reply other threads:[~2023-09-27 4:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 14:48 Projects for the next Outreachy round Christian Couder
2023-09-26 16:39 ` Kousik Sanagavarapu
2023-09-27 6:26 ` Christian Couder
2023-09-26 17:18 ` Victoria Dye
2023-09-27 6:18 ` Christian Couder
2023-09-26 22:23 ` Emily Shaffer
2023-09-27 6:14 ` Christian Couder
2023-09-27 3:30 ` Shuqi Liang [this message]
2023-09-27 6:33 ` Christian Couder
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=CAMO4yUEws6CmBH+rYynnGGsX067iJRgyQwVxa2b4mkYwnV_u+A@mail.gmail.com \
--to=cheskaqiqi@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=nasamuffin@google.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).