Re: Submodule/contents conflict
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 25, 2017, 02:12 UTC
- Message-ID
- <xmqqfugxxmkn.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <CAGZ79kZ5440r1EHOVP3eXxe5u=u16y_jXTA0C4hLJA2kUkF-kg@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
Show 5 quoted lines
> A similar bug report > https://public-inbox.org/git/CAG0BQX=wvpkJ=PQWV-NbmhuPV8yzvd_KYKzJmsfWq9xStZ2bnQ@mail.gmail.com/ > > "checkout --recurse-submodules" (as mentioned in that report) > made it into Git by now, but this bug goes unfixed, still.
I do not mind reverting that merge out of 'master'. Please holler if you feel these "go recursive" topics are premature.
Thanks.