From: "John Lin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] status: remove the empty line after hints
Date: Wed, 15 May 2019 03:54:02 -0700 (PDT) [thread overview]
Message-ID: <pull.196.git.gitgitgadget@gmail.com> (raw)
Before this patch, there is inconsistency between the status messages with
hints and the ones without hints: there is an empty line between the title
and the file list if hints are presented, but there isn't one if there are
no hints.
This patch remove the inconsistency by removing the empty lines even if
hints are presented.
John Lin (1):
status: remove the empty line after hints
t/t7060-wtstatus.sh | 5 ----
t/t7508-status.sh | 62 ------------------------------------------
t/t7512-status-help.sh | 14 ----------
wt-status.c | 4 ---
4 files changed, 85 deletions(-)
base-commit: ab15ad1a3b4b04a29415aef8c9afa2f64fc194a2
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-196%2Fjohnlinp%2Ffix-status-empty-line-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-196/johnlinp/fix-status-empty-line-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/196
--
gitgitgadget
next reply other threads:[~2019-05-15 10:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 10:54 John Lin via GitGitGadget [this message]
2019-05-15 10:54 ` [PATCH 1/1] status: remove the empty line after hints John Lin via GitGitGadget
2019-05-28 7:42 ` 林自均
2019-05-28 20:40 ` Junio C Hamano
2019-05-28 23:08 ` 林自均
2019-05-29 11:51 ` Johannes Schindelin
2019-06-01 1:12 ` 林自均
2019-06-03 14:17 ` Johannes Schindelin
2019-06-03 15:06 ` 林自均
2019-06-04 13:37 ` Johannes Schindelin
2019-06-04 14:02 ` [PATCH v2 0/1] " John Lin via GitGitGadget
2019-06-04 14:02 ` [PATCH v2 1/1] " John Lin via GitGitGadget
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=pull.196.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).