From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
josef@kufner.cz, "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH 0/2] Log pretty format alignment improvements
Date: Thu, 16 Jun 2016 20:18:36 +0700 [thread overview]
Message-ID: <20160616131838.14440-1-pclouds@gmail.com> (raw)
The first patch was from a long time ago. The concern was it may be
breaking existing user expectation [1]. I still maintain that it's a good
thing to do and should not break anything. Hence the resubmission.
The second patch adds negative column specifier to >|() and friends.
A positive number 'n' specifies the n-th column from the left border
of the screen, '-n' specifies the n-th column from the _right_ border.
I have been happy with 2/2 improving my "git l1" (fancy --oneline)
printout for many months. It's definitely a good thing to do in my
opinion.
[1] http://thread.gmane.org/gmane.comp.version-control.git/277710/focus=278326
Josef Kufner (1):
pretty: pass graph width to pretty formatting for use in '%>|(N)'
Nguyễn Thái Ngọc Duy (1):
pretty.c: support <direction>|(<negative number>) forms
commit.h | 1 +
graph.c | 7 ++++++
graph.h | 5 ++++
log-tree.c | 2 ++
pretty.c | 9 ++++++-
t/t4205-log-pretty-formats.sh | 57 +++++++++++++++++++++++++++++++++++++++++++
6 files changed, 80 insertions(+), 1 deletion(-)
--
2.8.2.524.g6ff3d78
next reply other threads:[~2016-06-16 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 13:18 Nguyễn Thái Ngọc Duy [this message]
2016-06-16 13:18 ` [PATCH 1/2] pretty: pass graph width to pretty formatting for use in '%>|(N)' Nguyễn Thái Ngọc Duy
2016-06-16 13:18 ` [PATCH 2/2] pretty.c: support <direction>|(<negative number>) forms Nguyễn Thái Ngọc Duy
2016-06-16 18:25 ` [PATCH 0/2] Log pretty format alignment improvements Junio C Hamano
2016-06-17 11:27 ` Duy Nguyen
2016-06-17 16:43 ` Junio C Hamano
2016-06-17 17:24 ` Josef Kufner
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=20160616131838.14440-1-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=josef@kufner.cz \
/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.