On Sun, Oct 25, 2026 at 4:11 PM Jacob Keller
[off-list ref] wrote:
Yep, that lays out the full reasoning for why you'd want this. Forking
the main repository could end up with broken submodule URLs unless you
*also* fork the submodules. Depending on your project you may (or may
not) want to do that, so having the option to use ^/ is good. Of
course using "^/" would mean that forking both super and subproject
would potentially break, until/unless you update your fork to point to
the new fork URL. I guess that is more semantically correct, your fork
of a super project woudl only change once you officially tell it to
move to the appropriate fork.
Yes, that's intended. "^/" is for a submodule that stays where it is.
If both are forked together, "../lib.git" still does the right thing.
Thanks for the review!