From: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: [GSoC] Week 5 and week 6 status update
Date: Wed, 27 Jul 2022 15:52:51 +0800 [thread overview]
Message-ID: <834d6b3e-9f1e-c848-a584-0161c503a7d9@gmail.com> (raw)
In-Reply-To: <CAJyCBOSrhxbCcDX5oWBuNEWOxQu2Rmk+T+paORLzoLF=iaBH1Q@mail.gmail.com>
Hi Git community,
Here is Shaoxuan Yuan.
I'm writing to share my latest progress [1] from GSoC week 5 and week 6.
You can read them when you are free, and generously give me some
advice if possible!
---
Summary of the two weeks
At this stage, the main focus is on making `git-sparse-checkout` work
better with `git-mv`. After getting the "from out-of-cone to in-cone"
series merged [2] into master, I'm working to make the complementary
"from in-cone to out-of-cone" [3] possible. It's now a [PATCH v1].
Read the previous blogs on GSoC to get a better context.
In the meantime, I'm also experimenting with `git-rm` to integrate with
`sparse-index`. `git-rm` turns out to be a slightly less complex command
in terms of its interaction with `sparse-checkout`, so working with it
at the same time gives me some insight into `sparse-index`, without
worrying too much about its compatibility with `sparse-checkout`.
[1] https://ffyuanda.github.io/blog/GSoC-week-5-6/
[2] https://github.com/git/git/commit/0455aad1e39f21acbaa8a84129fec8eb77682e0d
[3] https://lore.kernel.org/git/20220719132809.409247-1-shaoxuan.yuan02@gmail.com/
--
Thanks,
Shaoxuan
next prev parent reply other threads:[~2022-07-27 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 7:39 [GSoC] Status update Shaoxuan Yuan
2022-06-28 3:19 ` [GSoC] Week 2 status update Shaoxuan Yuan
2022-07-12 8:24 ` [GSoC] Week 3 and week 4 " Shaoxuan Yuan
2022-07-12 13:16 ` Derrick Stolee
2022-07-27 7:52 ` Shaoxuan Yuan [this message]
2022-08-08 11:30 ` [GSoC] Week 7 and week 8 " Shaoxuan Yuan
2022-08-17 10:07 ` [GSoC] Week 9 " Shaoxuan Yuan
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=834d6b3e-9f1e-c848-a584-0161c503a7d9@gmail.com \
--to=shaoxuan.yuan02@gmail.com \
--cc=git@vger.kernel.org \
/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).