From: SoutrikDas <valusoutrik@gmail.com>
To: lucasseikioshiro@gmail.com
Cc: ayu.chandekar@gmail.com, christian.couder@gmail.com,
git@vger.kernel.org, jltobler@gmail.com, karthik.188@gmail.com,
siddharthasthana31@gmail.com, valusoutrik@gmail.com
Subject: Re: [GSOC RFC PATCH] builtin/repo: add path.in-worktree field
Date: Fri, 27 Feb 2026 09:21:22 +0530 [thread overview]
Message-ID: <20260227035122.5588-1-valusoutrik@gmail.com> (raw)
In-Reply-To: <BEE3B56B-F8E0-43B5-95EA-8506A84CB2EA@gmail.com>
> I don't think this is small enough to count as a microproject. 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.
My bad, by microproject I meant this :
> GSoc 2026 Idea : Improve the new git repo command
>
> Getting started: Build Git from source, experiment with git repo info
> and git repo structure commands, study the implementation in builtin/repo.c,
> review the initial GSoC proposal and discussions, compare functionality
> with git rev-parse and identify gaps, and submit a *micro-patch to
> demonstrate familiarity with the codebase*.
I guess I misunderstood, I thought a relevant micropatch to the project
idea area ( ie repo.c ) had to be submitted along with a general microproject.
I did submit one code microproject [1] and a doc-fix [2]
> 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.
Now since a microproject in the gsoc idea domain is not mandatory ...
I think it would be okay to start on this ?
Regardless of it being fully reviewed, I feel like I should do some work
on repo.c before writing a gsoc proposal. That way I can better formulate
a timeline, maybe.
> Yeah, but then we would need to change all the calls to it, using
> the_repository at first. But I really don't know, I'll leave this
> discussion for more experienced people.
Alright.
> You can take a look on how `git rev-parse --is-inside-work-tree` is
> being tested today and use it as a base, since
> `git repo info path.is-inside-work-tree` would return true or false
> in the same situations.
Right, I dont know why I didn't do that, I will do that and send a patch v2
[1] : 20260209172445.39536-1-valusoutrik@gmail.com
[2] : pull.2187.git.git.1770293021383.gitgitgadget@gmail.com
prev parent reply other threads:[~2026-02-27 3:51 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
2026-02-27 3:51 ` SoutrikDas [this message]
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=20260227035122.5588-1-valusoutrik@gmail.com \
--to=valusoutrik@gmail.com \
--cc=ayu.chandekar@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jltobler@gmail.com \
--cc=karthik.188@gmail.com \
--cc=lucasseikioshiro@gmail.com \
--cc=siddharthasthana31@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