From: "Stephen P. Smith" <ischis2@cox.net>
To: Junio C Hamano <gitster@pobox.com>
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: Wed, 21 Nov 2018 19:08:21 -0700 [thread overview]
Message-ID: <2775489.rJSdpldxyu@thunderbird> (raw)
In-Reply-To: <xmqq8t1l6hve.fsf@gitster-ct.c.googlers.com>
On Wednesday, November 21, 2018 6:06:13 PM MST Junio C Hamano wrote:
> "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;
I was trying to decide if you were wanting someone besides Linus to carry this
through (knowing that he was unlikely to do so). The idea seems reasonable
to me. I don't mind doing so if neither of you object.
>
> - 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 wouldn't think this would go in now since the patch has been stalled for
months. It is also on the pu branch.
> > 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.
Picking up someones stalled patch is one thing, picking up Linus' patch is in
a different league.
next prev parent reply other threads:[~2018-11-22 2:08 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
2018-11-22 2:08 ` Stephen P. Smith [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2775489.rJSdpldxyu@thunderbird \
--to=ischis2@cox.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.