From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Cc: SoutrikDas <valusoutrik@gmail.com>,
ayu.chandekar@gmail.com, christian.couder@gmail.com,
git@vger.kernel.org, jltobler@gmail.com, karthik.188@gmail.com,
siddharthasthana31@gmail.com
Subject: Re: [GSOC RFC PATCH] builtin/repo: add path.in-worktree field
Date: Mon, 2 Mar 2026 23:38:10 +0530 [thread overview]
Message-ID: <96d93ef3-7843-4be7-925e-202888670373@gmail.com> (raw)
In-Reply-To: <xmqqtsv3uoc4.fsf@gitster.g>
Hi Junio,
On 27/02/26 04:03, Junio C Hamano wrote:
> Lucas Seiki Oshiro <lucasseikioshiro@gmail.com> writes:
> 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.
>
Thank you for your suggestions. We've tried to tweak the micro-project
page to remove the stale ones.
https://git.github.io/SoC-2026-Microprojects/
Feel free to let us know if you have any further suggestions.
--
Sivaraam
next prev parent reply other threads:[~2026-03-02 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 19:03 [GSOC RFC PATCH] builtin/repo: add path.in-worktree field SoutrikDas
2026-02-25 19:37 ` Lucas Seiki Oshiro
2026-02-26 20:16 ` SoutrikDas
2026-02-26 21:26 ` Lucas Seiki Oshiro
2026-02-26 22:33 ` Junio C Hamano
2026-02-26 22:38 ` Lucas Seiki Oshiro
2026-03-02 18:08 ` Kaartic Sivaraam [this message]
2026-02-27 3:51 ` SoutrikDas
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=96d93ef3-7843-4be7-925e-202888670373@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=ayu.chandekar@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jltobler@gmail.com \
--cc=karthik.188@gmail.com \
--cc=lucasseikioshiro@gmail.com \
--cc=siddharthasthana31@gmail.com \
--cc=valusoutrik@gmail.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