git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Stephen P. Smith" <ischis2@cox.net>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: What's cooking in git.git (Nov 2018, #06; Wed, 21)
Date: Thu, 22 Nov 2018 10:06:13 +0900	[thread overview]
Message-ID: <xmqq8t1l6hve.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <1965413.u7ZHvrJggb@thunderbird> (Stephen P. Smith's message of "Wed, 21 Nov 2018 16:54:04 -0700")

"Stephen P. Smith" <ischis2@cox.net> writes:

> On Wednesday, November 21, 2018 2:00:16 AM MST Junio C Hamano wrote:
>> [Stalled]
>> 
>> * lt/date-human (2018-07-09) 1 commit
>>  - Add 'human' date format
>> 
>>  A new date format "--date=human" that morphs its output depending
>>  on how far the time is from the current time has been introduced.
>>  "--date=auto" can be used to use this new format when the output is
>>  goint to the pager or to the terminal and otherwise the default
>>  format.
>
> What needs to be done with this patch to move it along?

In a random order as they come to my mind:

 - Support by people other than the original author;

 - Deciding what to call this (i.e. Linus's personal preference
   would not be the only 'human' style, but we may declare it is
   good enough as "a" human format, not "the" human format);

 - Some mechanism (either technical or documentation) to prevent
   endless stream of "I like human output, but I'd tweak it slightly
   this way" updates in the future;

 - Doc;

 - Command line completion;

 - Tests;

 - Waiting for the end of feature freeze before the upcoming
   release.

There may be others, but without all of the above, I'd feel a bit
uncomfortable.

> I see that both Linus and Junio have signed the patch.  

That does not assert that the code is desirable thing to add.  It
just says we made sure that we legally have rights to include it, if
we want to.

  reply	other threads:[~2018-11-22  1:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21  9:00 What's cooking in git.git (Nov 2018, #06; Wed, 21) Junio C Hamano
2018-11-21 10:48 ` Ævar Arnfjörð Bjarmason
2018-11-22 17:53   ` Jeff King
2018-11-22 18:36     ` Ævar Arnfjörð Bjarmason
2018-11-24 12:09       ` Jeff King
2018-11-25  2:02         ` Junio C Hamano
2018-11-26 18:13           ` Jeff King
2018-11-24  2:11     ` Junio C Hamano
2018-11-24 12:06       ` Jeff King
2018-11-21 20:11 ` js/vsts-ci, was " Johannes Schindelin
2018-11-21 23:54 ` Stephen P. Smith
2018-11-22  1:06   ` Junio C Hamano [this message]
2018-11-22  2:08     ` Stephen P. Smith
2018-11-22 16:05       ` Linus Torvalds
2018-11-22 10:48   ` Ævar Arnfjörð Bjarmason
2018-11-26 21:57 ` Stefan Beller
2018-11-26 23:34   ` Junio C Hamano
2018-12-05 22:04 ` Matthew DeVore

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=xmqq8t1l6hve.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ischis2@cox.net \
    --cc=torvalds@linux-foundation.org \
    /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).