Re: Submodule/contents conflict
- From
Stefan Beller <sbeller@google.com>
- Date
- Apr 25, 2017, 15:57 UTC
- Message-ID
- <CAGZ79kbr_LJ+mviXWxdyDWgSjAdc8VAXtfE_NG9qVOOCBM=JVQ@mail.gmail.com>
- In-Reply-To
- <xmqqfugxxmkn.fsf@gitster.mtv.corp.google.com>
On Mon, Apr 24, 2017 at 7:12 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 10 quoted lines
> Stefan Beller <sbeller@google.com> writes: > >> 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.
The bugs reported here are not for the recursive checkout, I was merely noting it as a side effect of time having passed. :)
I did not imply the recursive topics being premature.
Thanks, Stefan