From: Thomas Gummerer <t.gummerer@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: What's cooking in git.git (Jan 2019, #05; Tue, 29)
Date: Tue, 5 Feb 2019 20:42:08 +0000 [thread overview]
Message-ID: <20190205204208.GC6085@hank.intra.tgummerer.com> (raw)
In-Reply-To: <xmqqh8djtf6n.fsf@gitster-ct.c.googlers.com>
On 02/04, Junio C Hamano wrote:
> Thomas Gummerer <t.gummerer@gmail.com> writes:
>
> > There was also some discussion around the naming of the option, but I
> > don't have a strong opinion on that, so I'm happy with keeping the
> > --[no-]overlay option. I just wanted to bring it up again here in
> > case someone had a very strong opinion, and would prefer it being
> > changed before this goes into 2.21. (Not sure if I'm too late for the
> > series going to master).
>
> I do not mind leaving this topic out of 'master' for now, if that
> would help migrate people only once instead of twice. I think the
> real UI improvement would come with the new pair of commands split
> out of here, "switch-branches" and "restore-files", which will not
> happen within the timeframe of the current cycle anyway.
Agreed, I don't mind having this topic wait a little longer until
"restore-files" actually becomes a thing. Just keeping it in 'next'
for now sounds good to me.
> In any case, I think it is probably sensible to revert this step.
> Will queue; thanks.
prev parent reply other threads:[~2019-02-05 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 22:15 What's cooking in git.git (Jan 2019, #05; Tue, 29) Junio C Hamano
2019-01-30 19:07 ` Jeff Hostetler
2019-01-31 17:43 ` Junio C Hamano
2019-01-31 7:43 ` Denton Liu
2019-01-31 17:49 ` Junio C Hamano
2019-01-31 17:59 ` mk/use-size-t-in-zlib [was: Re: What's cooking in git.git (Jan 2019, #05; Tue, 29)] Thomas Braun
2019-01-31 20:38 ` Torsten Bögershausen
2019-02-04 21:13 ` What's cooking in git.git (Jan 2019, #05; Tue, 29) Thomas Gummerer
2019-02-04 21:30 ` Junio C Hamano
2019-02-05 20:42 ` Thomas Gummerer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190205204208.GC6085@hank.intra.tgummerer.com \
--to=t.gummerer@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox