From: Jeff King <peff@peff.net>
To: hIpPy <hippy2981@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Incorrect pipe for git log graph when using --name-status option
Date: Mon, 13 Feb 2017 16:51:07 -0500 [thread overview]
Message-ID: <20170213215107.7msmycclyslknpr2@sigill.intra.peff.net> (raw)
In-Reply-To: <CAM_JFCzniePuqJTFOy-odLfuKcBjssh0zk3PFBsVcm6Ww6iW5w@mail.gmail.com>
On Mon, Feb 13, 2017 at 01:43:45PM -0800, hIpPy wrote:
> With --name-status: I'm sorry if I nitpick here but I think the
> --name-status items should either be preceeded and followed by
> blank line OR not (as in oneline) but not just preceded (example
> below).
Yeah, I agree the output is a bit ugly.
I don't think there is a way to do what you want currently. The
--oneline code path has some internal magic that suppresses some of the
newlines.
I think it is a good goal that anything that can be expressed via one of
the regular formats (like --oneline) can be expressed via custom
formats. I don't know offhand how hard it would be to make this
particular case work. If somebody is interested in tackling this, they'd
probably need to dig around in pretty.c to see where the ONELINE code
path diverge from the USER_FORMAT one, and then figure out how a user
can specify that they want the ONELINE-ish semantics for their format.
-Peff
prev parent reply other threads:[~2017-02-13 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 2:49 Incorrect pipe for git log graph when using --name-status option hIpPy
2017-02-13 19:25 ` Junio C Hamano
2017-02-13 20:55 ` hIpPy
2017-02-13 21:16 ` Jeff King
2017-02-13 21:18 ` Junio C Hamano
2017-02-13 21:27 ` Jeff King
2017-02-13 21:43 ` hIpPy
2017-02-13 21:51 ` Jeff King [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170213215107.7msmycclyslknpr2@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hippy2981@gmail.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.
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).