From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Taylor Blau" <me@ttaylorr.com>,
git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: What's cooking in git.git (Mar 2020, #07; Sun, 22)
Date: Mon, 23 Mar 2020 14:17:00 -0600 [thread overview]
Message-ID: <20200323201700.GA98968@syl.local> (raw)
In-Reply-To: <xmqq4kue6fha.fsf@gitster.c.googlers.com>
On Mon, Mar 23, 2020 at 12:25:21PM -0700, Junio C Hamano wrote:
> Taylor Blau <me@ttaylorr.com> writes:
>
> > I noticed that this has been cooking in 'next' for a few weeks now. Is
> > there anything you're looking for specifically before graduating this to
> > master?
>
> Yeah, I saw some mention about "--input=none does not mean there is
> no input" confusion in a separate discussion in the past few days
> [*1*], which may make us reconsider the proposed UI by this series,
> and it is a good time to do so when we rewind/rebuild 'next' after
> a release (i.e. "now").
Makes sense. I hadn't responded to that thread yet because I thought
that it had already been discussed, but on second glance '--input=none'
really isn't as clear as it could be.
I posted [2], which I think should move things forward.
> [Reference]
>
> *1* https://lore.kernel.org/git/20200322110424.GC2224@szeder.dev/
Thanks,
Taylor
[2]: https://lore.kernel.org/git/e0f42a2f3c0162a5d43bb2bce0f69264b59f92e9.1584994172.git.me@ttaylorr.com/
prev parent reply other threads:[~2020-03-23 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 1:10 What's cooking in git.git (Mar 2020, #07; Sun, 22) Junio C Hamano
2020-03-23 19:16 ` Taylor Blau
2020-03-23 19:25 ` Junio C Hamano
2020-03-23 20:17 ` Taylor Blau [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=20200323201700.GA98968@syl.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder.dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.