Re: [PATCH 0/4] repo: add support for path-related fields

From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Date: Mar 8, 2026, 00:29 UTC
Message-ID: <041DCF2E-75FB-4B0A-9128-FDBB1A6DAC3C@gmail.com>
In-Reply-To: <aaSusXil9nDHYGMR@fruit.crustytoothpaste.net>

> I think you should provide both.  I originally added this for things
> like `--git-common-dir`, which Git LFS would really like to have as an
> absolute path in the way that Git canonicalizes it, as well as
> potentially a relative path.

Thanks for your input, brian!

> With `git rev-parse`, you can change `--path-format` on the command line
> between options, so if you want both, you just request one thing, use
> `--path-format`, and then request the other.  However, that can't be
> done with `git repo` and `--path-format`.

It makes sense. If we use the key format suggested by Ayush [1] we could retrieve both values with something like

   $ git repo info path.git-dir.absolute path.git-dir.relative

I'll stop by now. Since many people are interested in contributing to git-repo-info in GSoC, I'll leave this decision to the person who will work on it, if there is one.

[1] B46AA932-28EF-4A2C-96B9-0F05D9641C1C@gmail.com