From: Junio C Hamano <gitster@pobox.com>
To: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Cc: Pushkar Singh <pushkarkumarsingh1970@gmail.com>,
git@vger.kernel.org, karthiknayak@gmail.com, peff@peff.net,
jtobler@github.com, patrick@pks.im
Subject: Re: [PATCH 0/2] repo info: add path.git-dir and path.common-dir
Date: Mon, 02 Mar 2026 08:50:54 -0800 [thread overview]
Message-ID: <xmqqtsuy2n0x.fsf@gitster.g> (raw)
In-Reply-To: <8D232FDA-E286-48E7-8E41-ADC6645A9BC0@gmail.com> (Lucas Seiki Oshiro's message of "Sun, 1 Mar 2026 15:48:58 -0300")
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com> writes:
>> Hi,
>
> Hi!
>
>> Following the earlier RFC discussion about exposing repository
>> paths via `git repo info`, this series adds two new fields:
>>
>> - path.git-dir
>> - path.common-dir
>
> It's too early to send this. The first patch wasn't accepted yet
> (and I really don't think that it will be in v1)
What's happening here? To me, it looks as if many people are
stomping on each others' toes, adding path.something to "repo info"
output on their own without much inter-developer coordination.
prev parent reply other threads:[~2026-03-02 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 14:11 [RFC] git repo info: exposing repository paths Pushkar Singh
2026-02-11 12:18 ` Patrick Steinhardt
2026-02-18 18:35 ` Pushkar Singh
2026-03-01 13:44 ` [PATCH 0/2] repo info: add path.git-dir and path.common-dir Pushkar Singh
2026-03-01 13:59 ` [PATCH 1/2] repo: add the field path.git-dir Pushkar Singh
2026-03-01 14:03 ` [PATCH 2/2] repo: add the field path.common-dir Pushkar Singh
2026-03-01 16:50 ` [PATCH 0/2] repo info: add path.git-dir and path.common-dir K Jayatheerth
2026-03-01 18:48 ` Lucas Seiki Oshiro
2026-03-01 19:34 ` Pushkar Singh
2026-03-02 16:50 ` Junio C Hamano [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=xmqqtsuy2n0x.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jtobler@github.com \
--cc=karthiknayak@gmail.com \
--cc=lucasseikioshiro@gmail.com \
--cc=patrick@pks.im \
--cc=peff@peff.net \
--cc=pushkarkumarsingh1970@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