Re: [PATCH v3] repo: add paths.toplevel to repo info

From: Karthik Nayak <karthik.188@gmail.com>
Date: Apr 9, 2026, 16:01 UTC
Message-ID: <CAOLa=ZSwVbqWCo5PoUtZRx-bW-96tymL6TQp23BrRRrOveFrFg@mail.gmail.com>
In-Reply-To: <xmqq4ilkw5om.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

Show 10 quoted lines

> Karthik Nayak <karthik.188@gmail.com> writes:
>
>> Don't we still have to decide how we want to support relative vs
>> absolute paths? [1]
>
> I suspect more than just a few requests to this command yield
> path-valued response, so do we want an independent boolean "if we
> are showing a path, show it in relative (yes) or absolute (no)"
> option, or something?
>

I think there was some ideas around this:

  - Have a default mode and a way to swap it. Perhaps a boolean config
    on the command level
  - Output both the relative and absolute paths. So we'd have
    paths.toplevel.absolute
    paths.toplevel.relative
    or something like that.

Either ways, I think we should finalize the decision first, that way we don't have to have this discussion with each path-valued option.

Show 9 quoted lines

>> Also seeing that you're a GSoC candidate and this is part of the project
>> that you've (and other potential contributors) applied for, our
>> recommendation is to not start working on a project before the selection
>> process.
>
> Perhaps I should refrain from commenting on these patches to
> discourage the authors if that is the case.  I am not raising an
> objection, but do you have a pointer to the rationale behind the
> recommendation?

Officially the GSoC rules [1] only say:

  Any work done on the Project prior to acceptance of the Project Proposal
  will not be considered for Evaluations.

So there is no rule stopping a contributor from making such changes, and ultimately, open source projects benefit from contributions regardless of the contributor's application status.

However it gets confusing for other contributors who have proposals for the same topic, since they expect a certain status quo and a moving goal post makes it a lot harder.

[1]: https://summerofcode.withgoogle.com/rules