git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: jl/status-reduce-vertical-blank, was Re: What's cooking in git.git (Jul 2019, #02; Tue, 9)
Date: Wed, 10 Jul 2019 12:08:44 -0700	[thread overview]
Message-ID: <xmqq1ryxu2pv.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1907102058360.46@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 10 Jul 2019 20:59:21 +0200 (CEST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

>> * jl/status-reduce-vertical-blank (2019-06-21) 1 commit
>>  - status: remove the empty line after hints
>>
>>  Extra blank lines in "git status" output have been reduced.
>>
>>  Needs to wait on nd/switch-and-restore to stabilize.
>
> Didn't that latter branch hit `master` already, i.e. it did stabilize?

Hopefully ;-) 

I haven't used it very extensively myself (I am too used to typing
"git checkout"), so I wouldn't be surprised if people find glitches
in the updated experience after it hit 'master', though.

In any case, now we can decide whether we want to keep it and move
it forward, or it is a bad idea to be discarded.  My tentative vote
is to move it forward, fwiw.

Thanks.


      reply	other threads:[~2019-07-10 19:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10  3:28 What's cooking in git.git (Jul 2019, #02; Tue, 9) Junio C Hamano
2019-07-10 18:51 ` Johannes Schindelin
2019-07-10 18:58   ` Junio C Hamano
2019-07-11  0:02     ` Matheus Tavares Bernardino
2019-07-11 17:28       ` Junio C Hamano
2019-07-10 18:59 ` jl/status-reduce-vertical-blank, was " Johannes Schindelin
2019-07-10 19:08   ` Junio C Hamano [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

  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=xmqq1ryxu2pv.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /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).