git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSOC RFC PATCH] builtin/repo: add path.in-worktree field

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 26, 2026, 22:33 UTC
Message-ID
<xmqqtsv3uoc4.fsf@gitster.g>
In-Reply-To
<BEE3B56B-F8E0-43B5-95EA-8506A84CB2EA@gmail.com>
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com> writes:
Show 6 quoted lines
> A
> microproject is something simpler than that. See the microprojects
> page [1] for suggestions. They are more straightforward things that
> have more chances of being accepted quickly. And since having an accepted
> microproject is a mandatory step, you'll probably want it to be merged
> as soon as possible.

Microproject is to serve as a practice session for a new contributor to go through the patch submission + getting reviewed + sending polished version cycle. It does not have to result in a merge to the project, but it is essential to get reviewed and respond to reviews. How well you work with reviewers is the focus of the observation, and how complex the problem you tackle is is of much lessor importance.

Show 5 quoted lines
> I think that this seems to be easy to do, but the reviewing process
> may take some time, so it would be better if you stick to a
> one of the selected microprojects [1].
>
> [1] https://git.github.io/SoC-2024-Microprojects/

Is https://git.github.io/SoC-2026-Microprojects/ the latest? The above URL points at one a few years old.

Anyway, this list however might want a bit of updating.
 * I personally feel that "run_command*() to internal call" is way
   too involved for a microproject.  All the low-hanging frutis have
   already been picked in this area, I think.  That is why this does
   not appear in the list of microproject ideas in more recent
   years.
 * People seem to be finding more instances of "test -X" to replace
   with test_path_is_* helpers, so that would be fine to keep for
   now.
 * Ditto for "do not place git upstream of a pipe".
 * "Do not use signed int for collection of flag bits" may have
   outlived its usefulness, as it seems we are pushing more and more
   uses of enum for collection of flag bits.
Previous: Lucas Seiki OshiroNext: Lucas Seiki Oshiro
Message 5 of 8 in “builtin/repo: add path.in-worktree field”
  1. builtin/repo: add path.in-worktree fieldSoutrikDas, Feb 25, 2026
  2. Lucas Seiki OshiroFeb 25, 2026
  3. SoutrikDasFeb 26, 2026
  4. Lucas Seiki OshiroFeb 26, 2026
  5. Junio C HamanoFeb 26, 2026
  6. Lucas Seiki OshiroFeb 26, 2026
  7. Kaartic SivaraamMar 2, 2026
  8. SoutrikDasFeb 27, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.