ab/submodule-no-abspath (was Re: What's cooking in git.git (Nov 2022, #04; Fri, 18))
- From
Glen Choo <chooglen@google.com>
- Date
- Nov 21, 2022, 22:22 UTC
- Message-ID
- <kl6ltu2sdk1r.fsf@chooglen-macbookpro.roam.corp.google.com>
- In-Reply-To
- <Y3g95OYdwzq2OP3z@nand.local>
Taylor Blau <me@ttaylorr.com> writes:
Show 10 quoted lines
> * ab/submodule-no-abspath (2022-11-09) 1 commit > (merged to 'next' on 2022-11-18 at 34d0accc7b) > + submodule--helper absorbgitdirs: no abspaths in "Migrating git..." > (this branch is used by ab/remove--super-prefix.) > > Remove an absolute path in the "Migrating git directory" message. > > Will merge to 'master'. > source: <patch-1.1-34b54fdd9bb-20221109T020347Z-avarab@gmail.com> >
(Sorry, I should have spoken up before this got merged to 'next'.)
I have some reservations about this that I mentioned in [1], namely:
- Does this work correctly when using a worktree? - If "absorbgitdirs" becomes consistent with other "git submodule" subcommands and prints relative paths to submodules, then this produces the wrong result.
We probably won't see any complaints about this for a while, since submodules + worktrees are an uncommon combination, but I expect that we'll have to revert this at some point.
[1] https://lore.kernel.org/git/kl6lmt8qv9gc.fsf@chooglen-macbookpro.roam.corp.google.com