Re: [RFC PATCH] submodule: make '^/' work like '../' but with an absolute path
- From
- Stanislav Aleksandrov <lightofmysoul@gmail.com>
- Date
- Oct 30, 2026, 15:08 UTC
- Message-ID
- <20261030150806.3856050-1-lightofmysoul@gmail.com>
- In-Reply-To
- <CA+P7+xo8J_+3QECoGHnN1AxXPpjaKaHp3VoN9EEcyhZ+Q1fzew@mail.gmail.com>
On Sun, Oct 25, 2026 at 4:11 PM Jacob Keller <jacob.keller@gmail.com> wrote:
Show 9 quoted lines
> 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!