From: "Øyvind A. Holm" <sunny@sunbase.org>
To: git@vger.kernel.org
Cc: "Øyvind A. Holm" <sunny@sunbase.org>
Subject: [PATCH] wt-status.c: Expand cut_line so the scissor line is 72 chars
Date: Mon, 1 Sep 2014 02:07:25 +0200 [thread overview]
Message-ID: <1409530045-12866-1-git-send-email-sunny@sunbase.org> (raw)
Change the size of the commit scissor line to 72 characters (the
recommended maximum line length in log messages) so it can be used as a
visual clue in editors using monospaced fonts.
Signed-off-by: Øyvind A. Holm <sunny@sunbase.org>
---
Documentation/git-commit.txt | 2 +-
t/t7502-commit.sh | 2 +-
wt-status.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
index 0bbc8f5..d24573f 100644
--- a/Documentation/git-commit.txt
+++ b/Documentation/git-commit.txt
@@ -189,7 +189,7 @@ verbatim::
scissors::
Same as `whitespace`, except that everything from (and
including) the line
- "`# ------------------------ >8 ------------------------`"
+ "`# --------------------------------- >8 ---------------------------------`"
is truncated if the message is to be edited. "`#`" can be
customized with core.commentChar.
default::
diff --git a/t/t7502-commit.sh b/t/t7502-commit.sh
index 051489e..8b2ec6b 100755
--- a/t/t7502-commit.sh
+++ b/t/t7502-commit.sh
@@ -229,7 +229,7 @@ test_expect_success 'cleanup commit messages (scissors option,-F,-e)' '
cat >text <<EOF &&
# to be kept
-# ------------------------ >8 ------------------------
+# --------------------------------- >8 ---------------------------------
to be removed
EOF
echo "# to be kept" >expect &&
diff --git a/wt-status.c b/wt-status.c
index 27da529..010632c 100644
--- a/wt-status.c
+++ b/wt-status.c
@@ -18,7 +18,7 @@
#include "utf8.h"
static const char cut_line[] =
-"------------------------ >8 ------------------------\n";
+"--------------------------------- >8 ---------------------------------\n";
static char default_wt_status_colors[][COLOR_MAXLEN] = {
GIT_COLOR_NORMAL, /* WT_STATUS_HEADER */
--
2.1.0.29.g10a3b53
reply other threads:[~2014-09-01 0:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1409530045-12866-1-git-send-email-sunny@sunbase.org \
--to=sunny@sunbase.org \
--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.
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 NNTP newsgroup(s).