From: Jeff King <peff@peff.net>
To: "Kyle J. McKay" <mackyle@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH/RFC] git log --oneline alternative with dates, times and initials
Date: Thu, 29 Sep 2016 08:52:38 -0400 [thread overview]
Message-ID: <20160929125238.hifkxe7cmyebg64u@sigill.intra.peff.net> (raw)
In-Reply-To: <82EE6519-E58F-4382-87A5-55D9D1BBDCA9@gmail.com>
On Thu, Sep 29, 2016 at 04:00:06AM -0700, Kyle J. McKay wrote:
> > Each of those commits[1] needs some minor polish, and as I'm not really
> > that interested in fancy log output myself, I don't plan on working on
> > them further. I was mostly curious just how close we were. But if you'd
> > like to pursue it, feel free to use them as a starting point.
>
> Those patches are missing some of the features like showing root commits,
> handling two letter initials, showing the weekday, inserting a break where
> needed to avoid parent-child confusion in graph output and properly handling
> Duy's initials. :)
I'm not too surprised. I literally looked at the first screenshot from
your output and thought "surely git can do that with some minor tweaks".
Nor am I surprised that there are cases where the output is funny (99%
of the time I spent on it was tracking down that graph-padding bug).
I have no problem taking this in contrib or whatever, until a point when
Git is capable of doing the same thing itself. I just hoped to trick you
into working on Git. :)
-Peff
next prev parent reply other threads:[~2016-09-29 12:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 5:34 [PATCH/RFC] git log --oneline alternative with dates, times and initials Kyle J. McKay
2016-09-29 8:33 ` Jeff King
2016-09-29 8:33 ` [PATCH 1/5] pretty: allow formatting DATE_SHORT Jeff King
2016-09-30 6:17 ` Jacob Keller
2016-09-30 10:56 ` SZEDER Gábor
2016-09-30 22:04 ` Jacob Keller
2016-10-01 9:18 ` Jeff King
2016-09-29 8:36 ` [PATCH 2/5] pretty: allow formatting names as initials Jeff King
2016-09-29 17:31 ` Junio C Hamano
2016-09-29 17:32 ` Jeff King
2016-09-29 8:37 ` [PATCH 3/5] graph: fix extra spaces in graph_padding_line Jeff King
2016-09-29 8:38 ` [PATCH 4/5] graph: helper functions for printing commit header Jeff King
2016-09-29 8:38 ` [PATCH 5/5] log: add --commit-header option Jeff King
2016-09-29 17:49 ` Junio C Hamano
2016-09-29 18:31 ` Jeff King
2016-09-29 11:00 ` [PATCH/RFC] git log --oneline alternative with dates, times and initials Kyle J. McKay
2016-09-29 12:52 ` Jeff King [this message]
2016-09-29 17:38 ` Junio C Hamano
2016-09-29 18:30 ` Jeff King
2016-09-29 18:50 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160929125238.hifkxe7cmyebg64u@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mackyle@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).