git/list[1] front-page[2] threads[3] people[4] search[5] about
 

sb/submodule-recursive-checkout-detach-head

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 7, 2017, 02:00 UTC
Message-ID
<xmqq4lq6hmp2.fsf_-_@gitster.mtv.corp.google.com>
In-Reply-To
<CAGZ79kYUZv0g+3OEMrbT26A7mSLJzeS-yf5Knr-CnARHqVB=aQ@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
Show 17 quoted lines
>> * sb/submodule-recursive-checkout-detach-head (2017-07-28) 2 commits
>>   (merged to 'next' on 2017-10-26 at 30994b4c76)
>>  + Documentation/checkout: clarify submodule HEADs to be detached
>>  + recursive submodules: detach HEAD from new state
>>
>>  "git checkout --recursive" may overwrite and rewind the history of
>>  the branch that happens to be checked out in submodule
>>  repositories, which might not be desirable.  Detach the HEAD but
>>  still allow the recursive checkout to succeed in such a case.
>>
>>  Undecided.
>>  This needs justification in a larger picture; it is unclear why
>>  this is better than rejecting recursive checkout, for example.
> ...
> Detaching the submodule HEAD is in line with the current thinking
> of submodules, though I am about to send out a plan later
> asking if we want to keep it that way long term.

Did this "send out a plan" ever happen? I am about to rewind 'next' and rebuild on top of v2.15, and wondering if I should keep the topic or kick it back to 'pu' so that a better justification can be given.

Previous: Stefan BellerNext: Stefan Beller
Message 3 of 10 in “What's cooking in git.git (Oct 2017, #06; Fri, 27)”
  1. Junio C HamanoOct 27, 2017
  2. Stefan BellerOct 27, 2017
  3. sb/submodule-recursive-checkout-detach-headJunio C Hamano, Nov 7, 2017
  4. Stefan BellerNov 7, 2017
  5. Junio C HamanoNov 8, 2017
  6. Kaartic SivaraamOct 28, 2017
  7. Johannes SchindelinOct 29, 2017
  8. Junio C HamanoOct 29, 2017
  9. Johannes SchindelinOct 29, 2017
  10. Junio C HamanoOct 30, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.