From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, josef@kufner.cz
Subject: Re: [PATCH 0/2] Log pretty format alignment improvements
Date: Fri, 17 Jun 2016 18:27:07 +0700 [thread overview]
Message-ID: <20160617112707.GA29739@ash> (raw)
In-Reply-To: <xmqqtwgt3s9z.fsf@gitster.mtv.corp.google.com>
On Thu, Jun 16, 2016 at 11:25:28AM -0700, Junio C Hamano wrote:
> Nguyễn Thái Ngọc Duy <pclouds@gmail.com> writes:
>
> > 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.
>
> I do not think "it's a good feature to have" was a question from the
> beginning. Thread [1] stopped with me saying "as long as >(N) can
> be used as Duy claims as a workaround to get the original behaviour,
> it is good to allow using >|(N) for this new output format; I didn't
> check if >(N) does behave that way, though". What was necessary to
> resurrect the patch was "Yes, >(N) can be used that way and here is
> a test" or something like that.
Ah ok. This command with this series (using %>(n))
~/w/git/git log --format='%>(50,trunc)%s' --graph -15 origin/pu
and the system one at version 2.7.3 (using %>|(n))
/usr/bin/git log --format='%>|(50,trunc)%s' --graph -15 origin/pu
both produce the same output like this, checked with md5sum
* Merge branch 'js/am-3-merge-recursive-direct' in..
|\
| * am: make a direct call to merge_recursive
| * merge_recursive_options: introduce the "gently" ..
* | Merge branch 'tb/complete-status' into pu
|\ \
| * | completion: add git status
| * | completion: add __git_get_option_value helper
| * | completion: factor out untracked file modes into..
* | | Merge branch 'mj/log-show-signature-conf' into pu
|\ \ \
| * | | log: "--no-show-signature" commmand-line option
| * | | log: add "log.showsignature" configuration varia..
* | | | Merge branch 'nd/worktree-lock' into pu
|\ \ \ \
| * | | | worktree.c: find_worktree() search by path suffix
| * | | | worktree: add "unlock" command
| * | | | worktree: add "lock" command
| * | | | worktree.c: add is_worktree_locked()
The output looks weird though, which makes me a bit hesitate to add it
in the test suite...
--
Duy
next prev parent reply other threads:[~2016-06-17 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 13:18 [PATCH 0/2] Log pretty format alignment improvements Nguyễn Thái Ngọc Duy
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 [this message]
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=20160617112707.GA29739@ash \
--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 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).