From: Phillip Wood <phillip.wood123@gmail.com>
To: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>, git@vger.kernel.org
Cc: jltobler@gmail.com, lucasseikioshiro@gmail.com,
gitster@pobox.com, phillip.wood@dunelm.org.uk,
sandals@crustytoothpaste.net, kumarayushjha123@gmail.com,
a3205153416@gmail.com
Subject: Re: [GSoC][PATCH 0/4] teach git repo info to handle path keys
Date: Tue, 2 Jun 2026 14:03:17 +0100 [thread overview]
Message-ID: <8ebc3d98-40a5-4e99-a205-34254cf5172b@gmail.com> (raw)
In-Reply-To: <20260601151950.30686-1-jayatheerthkulkarni2005@gmail.com>
On 01/06/2026 16:19, K Jayatheerth wrote:
>
> So in patches 3 and 4, we add both `path.<field>.absolute` and
> `path.<field>.relative` for `gitdir` and `commondir`. Initially,
> it was proposed by Ayush to use `path.absolute.<field>`, but
> this would break the lexicographical order of the internal field
> array. I tweaked it to place the variant at the end as a suffix instead.
I don't understand the comment about breaking the lexicographical order,
surely it only breaks if the new items are added out of order? Why can't
we have
path.absolute.commondir
path.absolute.gitdir
path.relative.commondir
path.relative.gitdir
?
Thanks
Phillip
> There are still a few open questions that should be addressed
> by the community. I am tagging members who were involved in the
> previous discussions:
>
> Justin Tobler, Lucas Seiki Oshiro, Junio, Phillip Wood,
> brian m. carlson, and Ayush Jha.
>
> Apologies if I missed anyone; I included everyone who reviewed
> or participated in the discussions of Eslam's and Lucas's
> patches.
>
> Questions:
>
> 1. Should there still be a --path-format flag?
> 2. Should we consider a default option?
> Currently we have path.gitdir.absolute; should we consider
> an option where a plain path.gitdir returns some default?
> If yes:
> 2.1 Should we keep the default the same as rev-parse? Or
> should either relative or absolute be the default?
> 2.2 When printing using --all, should the default be
> printed, or should we print both absolute and
> relative?
> 3. Is printing both absolute and relative in a single call
> using --all acceptable?
> If no:
> 3.1 What's a better approach?
>
> I have discussed these changes with both Justin and Lucas
> internally. This series is presented to gather opinions from the
> wider community before moving forward.
>
> K Jayatheerth (4):
> path: add strbuf_add_path for formatting paths
> rev-parse: use strbuf_add_path for path formatting
> repo: add path.gitdir with absolute and relative suffix formatting
> repo: add path.commondir with absolute and relative suffix formatting
>
> Documentation/git-repo.adoc | 15 ++++++
> builtin/repo.c | 50 ++++++++++++++++++
> builtin/rev-parse.c | 100 ++++++++----------------------------
> path.c | 58 +++++++++++++++++++++
> path.h | 16 ++++++
> t/t1900-repo-info.sh | 32 ++++++++++++
> 6 files changed, 192 insertions(+), 79 deletions(-)
>
prev parent reply other threads:[~2026-06-02 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 15:19 [GSoC][PATCH 0/4] teach git repo info to handle path keys K Jayatheerth
2026-06-01 15:19 ` [GSoC][PATCH 1/4] path: add strbuf_add_path for formatting paths K Jayatheerth
2026-06-02 13:00 ` Phillip Wood
2026-06-01 15:19 ` [GSoC][PATCH 2/4] rev-parse: use strbuf_add_path for path formatting K Jayatheerth
2026-06-01 15:19 ` [GSoC][PATCH 3/4] repo: add path.gitdir with absolute and relative suffix formatting K Jayatheerth
2026-06-01 16:28 ` Lucas Seiki Oshiro
2026-06-01 23:09 ` Junio C Hamano
2026-06-01 15:19 ` [GSoC][PATCH 4/4] repo: add path.commondir " K Jayatheerth
2026-06-01 16:34 ` Lucas Seiki Oshiro
2026-06-01 21:58 ` Lucas Seiki Oshiro
2026-06-01 16:25 ` [GSoC][PATCH 0/4] teach git repo info to handle path keys Lucas Seiki Oshiro
2026-06-01 22:04 ` Lucas Seiki Oshiro
2026-06-01 23:05 ` Junio C Hamano
2026-06-02 13:03 ` Phillip Wood [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=8ebc3d98-40a5-4e99-a205-34254cf5172b@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=a3205153416@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jayatheerthkulkarni2005@gmail.com \
--cc=jltobler@gmail.com \
--cc=kumarayushjha123@gmail.com \
--cc=lucasseikioshiro@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=sandals@crustytoothpaste.net \
/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