How common would it be? Sorry, I don't know. Someone further down in that
SO article suggested your simple answer should work, but suggests that the
new command is preferred. Probably just my broken config.

According to that Stack Overflow article, that arg was added in git 2.13
(Q2 2017).

On Tue, May 12, 2020 at 3:28 PM Dmitry Gutov <dgutov@yandex.ru> wrote:

> On 12.05.2020 21:33, Gary Oberbrunner wrote:
> > In my case at least, you're right and my submodule is seriously
> > confused. It has a .git/ dir which disagrees with the ../.git/modules
> > one. That's what was causing my problem. I've been doing a lot of work
> > in that submodule (multiple upstream repos, merges, pushes, etc.) and
> > perhaps something I did made it create that.
>
> How common do you think is such problem going to be? If it's rare, I'd
> rather let you fix the local configuration and leave that part of the
> code in Emacs simple. Unless this comes up again, of course.
>
> > Apparently the correct way to do this is "git rev-parse
> > --show-superproject-working-tree". See
> > https://stackoverflow.com/questions/7359204  for more info. (And in
> > fact that does work in my case even with my messed-up .git dir in the
> > submodule.)
>
> Thank you. Any idea which version of Git this was added in first? We'd
> have to consider that for compatibility with older systems.
>


-- 
Gary