Re: [PATCH v6 00/10] Add submodulePathConfig extension and gitdir encoding

From: Ben Knoble <ben.knoble@gmail.com>
Date: Dec 13, 2025, 14:03 UTC
Message-ID: <34DD8798-5C69-4092-B6C9-6609E688FBE8@gmail.com>
In-Reply-To: <20251213080817.347922-1-adrian.ratiu@collabora.com>

Show 7 quoted lines

> Le 13 déc. 2025 à 03:09, Adrian Ratiu <adrian.ratiu@collabora.com> a écrit :
> 
> Hello everyone,
> 
> For those new to the series, we're implementing a submodule gitdir
> extension which allows us to have a unified way to determine gitdirs
> and do things like encode submodule paths to avoid FS conflicts.

Hi there, I admit I haven’t followed this series closely. I use submodules quite a bit but haven’t yet peered into the depths of the implementation.

I read over the documentation changes in this series, and it’s not clear to me how or why I would use this new feature (I don’t mean there’s no benefit! Just that I’m having a hard time parsing it out.). By “how” I mean: I can see how to set config and run the migrator; what does that unlock for me to now go and do?

Does one of the previous cover letters explain how this is useful to submodule users? If so which, and perhaps the docs could also contain a “here’s when/why you might want this extension enabled and what it allows you to do”?

Or maybe this is meant to be not too user-facing, in which case I’m curious who would turn this on and why still :)

Again, I am mostly curious, so please don’t read this as an attempt to hold the series hostage! :)

Best, Ben