From: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
Date: Fri, 20 Mar 2026 01:49:28 GMT
Subject: Re: [PATCH v6 0/6] repo info: add category/path keys and --path-format
Message-ID: <CA+rGoLdjCZfDnvyQ+qiJn4xhA7F5cj8Mouc+pG9vbrb6ngoxVQ@mail.gmail.com>
In-Reply-To: <58874877-D2F4-431E-82FD-722D8A2BC790@yahoo.com>

On Fri, Mar 20, 2026 at 2:03 AM Jerry Wang <jerrywang183@yahoo.com> wrote:
>
> Hi Jay,
>
> Thanks, this is very helpful.
>
> That makes sense. I agree that checking only
> repo_get_work_tree(repo) == NULL is too weak, and the
> "git -C <nonbare>/.git" case is a good example of that.
>
> I'll keep the linked-worktree / separate-git-dir coverage patch
> separate. For layout.bare, I'll first add tests to pin down the
> intended semantics, then follow up with a small repo-aware fix,
> likely with a repo_is_bare() helper if that turns out to be the
> right shape.
>
> Thanks,
> Jialong
>


If you are a GSoC applicant(I am presuming) I suggest not to start
working on patches
as you might step on other people's toes.

Similar discussion here [1]
Similar official info here [2] in the _Don’t work on a proposed
project right away_ section.
Another similar discussion [3]
Similar thing was caused by Eslam's patches which overlapped with what
Lucas had previously as a foundation [4].

Regards,
- Jayatheerth

1 - https://lore.kernel.org/git/pull.2242.git.git.1773766519857.gitgitgadget@gmail.com/T/#m9506e0856630c9ff962093d59cc9477bd39ea6df
2 - https://git.github.io/General-Microproject-Information/
3 - https://lore.kernel.org/git/CALE2CrTt_2-9C4zCrZPBabtsWY=+Mk-bH4Jaemk=yHtfpoLjfg@mail.gmail.com/T/#m002015a8042bfe2717887c3ada9afd645615f50a
4 - https://lore.kernel.org/git/CA+rGoLdTc2caDUsQedpegL+T4MqwwiA62uuDSFSawAT5vcPvWQ@mail.gmail.com/T/#t