From: Pushkar Singh <pushkarkumarsingh1970@gmail•com>
To: git@vger•kernel.org
Cc: gitster@pobox•com, karthiknayak@gmail•com,
lucasseikioshiro@gmail•com, patrick@pks•im, peff@peff•net,
Pushkar Singh <pushkarkumarsingh1970@gmail•com>
Subject: [PATCH 2/2] repo: add the field path.common-dir
Date: Sun, 1 Mar 2026 14:01:38 +0000 [thread overview]
Message-ID: <20260301140137.1072709-2-pushkarkumarsingh1970@gmail.com> (raw)
In-Reply-To: <0260301134412.1072596-2-pushkarkumarsingh1970@gmail.com>
Expose the repository common directory through a new
path.common-dir field in git repo info.
This mirrors the information available via
git rev-parse --common-dir and allows structured
retrieval through the repo subcommand.
The value respects the --path-format flag.
Signed-off-by: Pushkar Singh <pushkarkumarsingh1970@gmail•com>
---
builtin/repo.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/builtin/repo.c b/builtin/repo.c
index 8b4c7ae4cb..d42ac2478b 100644
--- a/builtin/repo.c
+++ b/builtin/repo.c
@@ -88,6 +88,21 @@ static int get_path_git_dir(struct repository *repo, struct strbuf *buf,
return 0;
}
+static int get_path_common_dir(struct repository *repo, struct strbuf *buf,
+ const char *prefix,
+ enum path_format_type format)
+{
+ const char *commondir = repo_get_common_dir(repo);
+
+ if (!commondir)
+ return error(_("unable to retrieve common directory"));
+
+ strbuf_add_path(buf, commondir, prefix, format,
+ PATH_DEFAULT_RELATIVE_IF_SHARED);
+
+ return 0;
+}
+
static int get_references_format(struct repository *repo, struct strbuf *buf,
const char *prefix UNUSED,
enum path_format_type format UNUSED)
@@ -102,6 +117,7 @@ static const struct repo_info_field repo_info_field[] = {
{ "layout.bare", get_layout_bare },
{ "layout.shallow", get_layout_shallow },
{ "object.format", get_object_format },
+ { "path.common-dir", get_path_common_dir },
{ "path.git-dir", get_path_git_dir },
{ "path.toplevel", get_path_toplevel },
{ "references.format", get_references_format },
--
2.43.0
next parent reply other threads:[~2026-03-01 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0260301134412.1072596-2-pushkarkumarsingh1970@gmail.com>
2026-03-01 14:01 ` Pushkar Singh [this message]
2026-03-01 13:44 [PATCH 0/2] repo info: add path.git-dir and path.common-dir Pushkar Singh
2026-03-01 14:03 ` [PATCH 2/2] repo: add the field path.common-dir Pushkar Singh
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=20260301140137.1072709-2-pushkarkumarsingh1970@gmail.com \
--to=pushkarkumarsingh1970@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=karthiknayak@gmail$(echo .)com \
--cc=lucasseikioshiro@gmail$(echo .)com \
--cc=patrick@pks$(echo .)im \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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