From: Stefan Beller <sbeller@google.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] recursive submodules: detach HEAD from new state
Date: Tue, 21 Nov 2017 15:00:08 -0800 [thread overview]
Message-ID: <CAGZ79kbNwV5dg2raUu4SZRWsocpXr7xtgDuyyQ+gVcPFQWfKjg@mail.gmail.com> (raw)
In-Reply-To: <20171121224709.GJ3429@aiede.mtv.corp.google.com>
On Tue, Nov 21, 2017 at 2:47 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hi,
>
> Stefan Beller wrote:
>> On Tue, Nov 21, 2017 at 2:34 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>
>>> Stefan, do you know what thread I should look at to find the current
>>> state of this patch? I've had it applied locally for a long time.
>>
>> It was "Undecided" for some time, then Junio kicked it back to pu, expecting a
>> reroll[1]. The "send out a plan" that was referenced is found in [2]
>> describing 6 plans for the future of submodules. The approach in [3]
>> which is different on the implementation level, but very similar on
>> the UX level sounds best currently. I'll coordinate with JTan to
>> come up with patches for that.
>>
>> [1] https://public-inbox.org/git/CAGZ79kYUZv0g+3OEMrbT26A7mSLJzeS-yf5Knr-CnARHqVB=aQ@mail.gmail.com/
>> [2] https://public-inbox.org/git/20171109001007.11894-1-sbeller@google.com/
>> [3] https://public-inbox.org/git/20171108172945.33c42a0e91b4ac494217b788@google.com/
>
> Thanks. That thread appears to be about a long-term plan; what is the
> short-term plan?
>
> E.g. is there any additional documentation that should be added to the
> patch that detaches?
The second patch in that series has a tiny bit of information, see
"Documentation/checkout: clarify submodule HEADs to be detached".
I would think that this is sufficient for the short term to get into a
safe state.
> Or should it go in as-is?
That is what I would prefer and then we'll build on top of this once we
figured out the direction of the long term solution.
Thanks,
Stefan
next prev parent reply other threads:[~2017-11-21 23:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 17:36 [PATCH] recursive submodules: detach HEAD from new state Stefan Beller
2017-07-24 18:03 ` Jonathan Nieder
2017-07-24 19:07 ` Stefan Beller
2017-07-24 20:57 ` Junio C Hamano
2017-07-24 21:33 ` Junio C Hamano
2017-07-24 22:23 ` Junio C Hamano
2017-07-25 22:27 ` Stefan Beller
2017-07-26 19:36 ` Junio C Hamano
2017-11-21 22:34 ` Jonathan Nieder
2017-11-21 22:45 ` Stefan Beller
2017-11-21 22:47 ` Jonathan Nieder
2017-11-21 23:00 ` Stefan Beller [this message]
2017-11-22 0:54 ` Junio C Hamano
Reply instructions:
You may reply publicly 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGZ79kbNwV5dg2raUu4SZRWsocpXr7xtgDuyyQ+gVcPFQWfKjg@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).