git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Kyle J. McKay" <mackyle@gmail.com>,
	Git mailing list <git@vger.kernel.org>
Subject: Re: [PATCH/RFC] git log --oneline alternative with dates, times and initials
Date: Thu, 29 Sep 2016 11:50:19 -0700	[thread overview]
Message-ID: <xmqqeg42fslw.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160929183006.exyaikr4ijiq5tp3@sigill.intra.peff.net> (Jeff King's message of "Thu, 29 Sep 2016 14:30:06 -0400")

Jeff King <peff@peff.net> writes:

> But I also buy the argument that contrib/ is simply a hassle. This
> script can live in its own repository somewhere, and handle
> announcements and patches on the list.

I think the output of this script is largely personal preference,
which can be made to a project preference for a project enough of
whose participant so desires.

For example, I would not be surprised if this appeared next to
checkpatch.pl script in the kernel archive.  When a project that
uses Git to store its sources finds a need to summarize its log in a
standardized way that is not produced natively by Git, such a
project may add this script to its scripts/ area, just like a
project that wants to have a standard way to help its contributors
to avoid common style errors a lot more than our "diff" (which only
highlights whitespace errors) does may ship checkpatch.pl in it.

So in that sense, while I do not mean to say that the script itself
must become a standalone project that has only one script in it, I
do not think it belongs "our" contrib/, as we do not see a need to
standardize its output as the log summary standard we the Git
project uses on its own history.

On the other hand, your illustration of the needed bits to express
this particular output format used by Kyle's script, when polished,
does fit in our codebase.  We are interested in making it possible
for projects and users to do more by using Git with its standard
customization features.

      reply	other threads:[~2016-09-29 18:50 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
2016-09-29 17:38       ` Junio C Hamano
2016-09-29 18:30         ` Jeff King
2016-09-29 18:50           ` Junio C Hamano [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=xmqqeg42fslw.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mackyle@gmail.com \
    --cc=peff@peff.net \
    /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).