mailing list mirror (one of many)
 help / Atom feed
From: Junio C Hamano <>
To: Stefan Beller <>
Cc: git <>
Subject: sb/submodule-recursive-checkout-detach-head
Date: Tue, 07 Nov 2017 11:00:57 +0900
Message-ID: <> (raw)
In-Reply-To: <>

Stefan Beller <> writes:

>> * 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

  reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27  8:32 What's cooking in git.git (Oct 2017, #06; Fri, 27) Junio C Hamano
2017-10-27 18:50 ` Stefan Beller
2017-11-07  2:00   ` Junio C Hamano [this message]
2017-11-07 17:05     ` sb/submodule-recursive-checkout-detach-head Stefan Beller
2017-11-08  0:21       ` sb/submodule-recursive-checkout-detach-head Junio C Hamano
2017-10-28 17:13 ` What's cooking in git.git (Oct 2017, #06; Fri, 27) Kaartic Sivaraam
2017-10-29 13:13 ` Johannes Schindelin
2017-10-29 14:18   ` Junio C Hamano
2017-10-29 15:18     ` Johannes Schindelin
2017-10-30  1:27       ` Junio C Hamano

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:
       or Tor2web:

AGPL code for this site: git clone public-inbox