* [GSoC] Week 2 status update
2022-06-15 7:39 [GSoC] Status update Shaoxuan Yuan
@ 2022-06-28 3:19 ` Shaoxuan Yuan
2022-07-12 8:24 ` [GSoC] Week 3 and week 4 " Shaoxuan Yuan
` (3 subsequent siblings)
4 siblings, 0 replies; 7+ messages in thread
From: Shaoxuan Yuan @ 2022-06-28 3:19 UTC (permalink / raw)
To: Git List
Hi Git community,
Here is Shaoxuan Yuan.
I'm writing to let you know about my previous GSoC blogs:
About GSoC 2022 [1]
GSoC Week 1 [2]
GSoC Week 2 [3]
[1] https://ffyuanda.github.io/blog/GSoC/
[2] https://ffyuanda.github.io/blog/GSoC-week-1/
[3] https://ffyuanda.github.io/blog/GSoC-week-2/
From now on, I will reply to this thread to send weekly blog updates.
You can read them when you are free, and generously give me some
advice if possible!
Thanks & Regards,
Shaoxuan
^ permalink raw reply [flat|nested] 7+ messages in thread
* [GSoC] Week 3 and week 4 status update
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 ` Shaoxuan Yuan
2022-07-12 13:16 ` Derrick Stolee
2022-07-27 7:52 ` [GSoC] Week 5 and week 6 " Shaoxuan Yuan
` (2 subsequent siblings)
4 siblings, 1 reply; 7+ messages in thread
From: Shaoxuan Yuan @ 2022-07-12 8:24 UTC (permalink / raw)
To: Git List
Hi Git community,
Here is Shaoxuan Yuan.
I'm writing to share my latest progress [1] from GSoC week 3 and week 4.
You can read them when you are free, and generously give me some
advice if possible!
---
Summary of the week 3 and week 4
At this stage, the main focus is on making `git-sparse-checkout` work better
with `git-mv`. With the ongoing "from out-of-cone to in-cone" clearing
up, I'm also working to make the complementary "from in-cone to out-of-cone"
possible. Read the previous blogs on GSoC to get a better context.
In the meantime, some experiments towards integration with `sparse-index`
have also started, which are based on the latest work "from in-cone to
out-of-cone" boiling in my branch.
This week I'm working to ship a PATCH v5 [2] (please reference all the
code here) to address the issues raised in PATCH v4 [3].
The good news is, that PATCH v5 is being queued into the 'next' branch,
which
means it could potentially be merged into 'master'. It marks that this stage
of work is almost done.
[1] https://ffyuanda.github.io/blog/GSoC-week-3-4/
[2]
https://lore.kernel.org/git/20220630023737.473690-1-shaoxuan.yuan02@gmail.com/
[3]
https://lore.kernel.org/git/20220623114120.12768-1-shaoxuan.yuan02@gmail.com/
Thanks & Regards,
Shaoxuan
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [GSoC] Week 3 and week 4 status update
2022-07-12 8:24 ` [GSoC] Week 3 and week 4 " Shaoxuan Yuan
@ 2022-07-12 13:16 ` Derrick Stolee
0 siblings, 0 replies; 7+ messages in thread
From: Derrick Stolee @ 2022-07-12 13:16 UTC (permalink / raw)
To: Shaoxuan Yuan, Git List
On 7/12/22 2:24 AM, Shaoxuan Yuan wrote:
> Hi Git community,
>
> Here is Shaoxuan Yuan.
>
> I'm writing to share my latest progress [1] from GSoC week 3 and week 4.
Thanks for the report!
> This week I'm working to ship a PATCH v5 [2] (please reference all the
> code here) to address the issues raised in PATCH v4 [3].
(I think this is left over from earlier?)
> The good news is, that PATCH v5 is being queued into the 'next' branch, which
> means it could potentially be merged into 'master'. It marks that this stage
> of work is almost done.
In fact, the latest "What's Cooking" says this:
* sy/mv-out-of-cone (2022-07-01) 8 commits
(merged to 'next' on 2022-07-08 at 654970fdb7)
+ mv: add check_dir_in_index() and solve general dir check issue
+ mv: use flags mode for update_mode
+ mv: check if <destination> exists in index to handle overwriting
+ mv: check if out-of-cone file exists in index with SKIP_WORKTREE bit
+ mv: decouple if/else-if checks using goto
+ mv: update sparsity after moving from out-of-cone to in-cone
+ t1092: mv directory from out-of-cone to in-cone
+ t7002: add tests for moving out-of-cone file/directory
"git mv A B" in a sparsely populated working tree can be asked to
move a path between directories that are "in cone" (i.e. expected
to be materialized in the working tree) and "out of cone"
(i.e. expected to be hidden). The handling of such cases has been
improved.
Will merge to 'master'.
source: <20220630023737.473690-1-shaoxuan.yuan02@gmail.com>
So, it is already in 'next' and will merge to 'master' soon. You
should expect those commits to be final (barring anything drastic
noticed during the cooking phase) so you can send your next set
of patches. Just make sure to point out in the cover letter that
they are based on sy/mv-out-of-cone. That branch is available in
the gitgitgadget/git repository so you can base a PR against it,
if you want.
Thanks,
-Stolee
^ permalink raw reply [flat|nested] 7+ messages in thread
* [GSoC] Week 5 and week 6 status update
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-27 7:52 ` Shaoxuan Yuan
2022-08-08 11:30 ` [GSoC] Week 7 and week 8 " Shaoxuan Yuan
2022-08-17 10:07 ` [GSoC] Week 9 " Shaoxuan Yuan
4 siblings, 0 replies; 7+ messages in thread
From: Shaoxuan Yuan @ 2022-07-27 7:52 UTC (permalink / raw)
To: Git List
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* [GSoC] Week 7 and week 8 status update
2022-06-15 7:39 [GSoC] Status update Shaoxuan Yuan
` (2 preceding siblings ...)
2022-07-27 7:52 ` [GSoC] Week 5 and week 6 " Shaoxuan Yuan
@ 2022-08-08 11:30 ` Shaoxuan Yuan
2022-08-17 10:07 ` [GSoC] Week 9 " Shaoxuan Yuan
4 siblings, 0 replies; 7+ messages in thread
From: Shaoxuan Yuan @ 2022-08-08 11:30 UTC (permalink / raw)
To: Git List
Hi Git community,
Here is Shaoxuan Yuan.
I'm writing to share my latest progress [1] from GSoC week 7 and week 8.
You can read it when you are free, and generously give me some
advice if possible!
---
Summary
In the past two weeks, besides keeping the work on `git-mv`, I was
also working on the sparse-index integration with `git-rm`. I shipped
one iteration of `git-mv` series and two iterations of `git-rm`
series. At the time of writing, `git-mv` is v2 and `git-rm` is also v2.
[1] https://ffyuanda.github.io/blog/GSoC-week-7-8/
--
Thanks,
Shaoxuan
^ permalink raw reply [flat|nested] 7+ messages in thread
* [GSoC] Week 9 status update
2022-06-15 7:39 [GSoC] Status update Shaoxuan Yuan
` (3 preceding siblings ...)
2022-08-08 11:30 ` [GSoC] Week 7 and week 8 " Shaoxuan Yuan
@ 2022-08-17 10:07 ` Shaoxuan Yuan
4 siblings, 0 replies; 7+ messages in thread
From: Shaoxuan Yuan @ 2022-08-17 10:07 UTC (permalink / raw)
To: Git List
Hi Git community,
Here is Shaoxuan Yuan.
I'm writing to share my latest progress [1] from GSoC week 9.
You can read it when you are free, and generously give me some
advice if possible!
[1] https://ffyuanda.github.io/blog/GSoC-week-9/
---
Summary
In week 9, I did two things:
1. Send out a v3 for `git mv` (from-in-to-out).
2. Explore `git grep` and try to integrate with sparse index.
Good news this week:
1. `rm` is in the `next` branch, hooray!
I found that a verbatim development log is both hard to write and read,
so I decided that I should only catch the interesting moments which may
be educational or amusing :)
--
Thanks,
Shaoxuan
^ permalink raw reply [flat|nested] 7+ messages in thread