Re: Incorrect pipe for git log graph when using --name-status option

From: Jeff King <peff@peff.net>
Date: Feb 13, 2017, 21:51 UTC
Message-ID: <20170213215107.7msmycclyslknpr2@sigill.intra.peff.net>
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