git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Nov 2018, #06; Wed, 21)

From
SSStephen P. Smith <ischis2@cox.net>
Date
Nov 22, 2018, 02:08 UTC
Message-ID
<2775489.rJSdpldxyu@thunderbird>
In-Reply-To
<xmqq8t1l6hve.fsf@gitster-ct.c.googlers.com>
On Wednesday, November 21, 2018 6:06:13 PM MST Junio C Hamano wrote:
Show 19 quoted lines
> "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.

Show 21 quoted lines
> 
>  - 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.

Show 5 quoted lines
> > 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.

Previous: Junio C HamanoNext: Linus Torvalds
Message 13 of 18 in “What's cooking in git.git (Nov 2018, #06; Wed, 21)”
  1. Junio C HamanoNov 21, 2018
  2. Ævar Arnfjörð BjarmasonNov 21, 2018
  3. Jeff KingNov 22, 2018
  4. Ævar Arnfjörð BjarmasonNov 22, 2018
  5. Jeff KingNov 24, 2018
  6. Junio C HamanoNov 25, 2018
  7. Jeff KingNov 26, 2018
  8. Junio C HamanoNov 24, 2018
  9. Jeff KingNov 24, 2018
  10. js/vsts-ci, was Re: What's cooking in git.git (Nov 2018, #06; Wed, 21)Johannes Schindelin, Nov 21, 2018
  11. Stephen P. SmithNov 21, 2018
  12. Junio C HamanoNov 22, 2018
  13. Stephen P. SmithNov 22, 2018
  14. Linus TorvaldsNov 22, 2018
  15. Ævar Arnfjörð BjarmasonNov 22, 2018
  16. Stefan BellerNov 26, 2018
  17. Junio C HamanoNov 26, 2018
  18. Matthew DeVoreDec 5, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.