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: eletuchy@gmail.com, git@vger.kernel.org, eletuchy@facebook.com,
	Eugene Letuchy <eugene@facebook.com>
Subject: Re: [PATCH 2/2] --date=relative falls back to "short" format for commits older than a year
Date: Mon, 23 Feb 2009 08:33:37 -0800	[thread overview]
Message-ID: <7v8wnxun8e.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20090223031631.GC22348@coredump.intra.peff.net

Jeff King <peff@peff.net> writes:

> I thought about that, but I wanted to keep the maximum size down for
> column output (like in git-blame). Which is why I bumped the "use
> months" limit to 24 months instead of 12.
>
> And that limit can also be tweaked.  Surely at some point there is a
> range where you no longer care about the months and "N years" has high
> enough resolution. But there is also a point where "N months" gets
> cumbersome (75 months is a more annoying than "around 6 years"). The
> question is whether we reach the "cumbersome" point before we reach the
> "don't care about months" point.

Yes, "75 months" is unacceptable.  I suspect people's mind would not work
well with anything larger than 60 months.  I've actually thought about
"don't care about months" point, but 12 months is a long time.  You
certainly remember there still was a noticeable maturity difference
between classmates who were born in the earliest months of the school year
and in the last months before graduating grade school.  Perhaps after 20
years.

> Another option would to give higher resolution in number of years, like
> "3.5 years" or even "3.1 years".

But I do not think people think of years in terms of decimal fraction.

  parent reply	other threads:[~2009-02-23 16:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 21:23 [PATCH 2/2] --date=relative falls back to "short" format for commits older than a year eletuchy
2009-02-20 22:15 ` Linus Torvalds
2009-02-20 22:47   ` Eugene Letuchy
2009-02-21  5:48   ` Junio C Hamano
2009-02-22 23:06 ` Jeff King
2009-02-23  1:44   ` Junio C Hamano
2009-02-23  3:16     ` Jeff King
2009-02-23  8:09       ` Marius Storm-Olsen
2009-02-24  5:04         ` Jeff King
2009-02-24  6:35           ` Marius Storm-Olsen
2009-02-24  6:36             ` Jeff King
2009-02-23 16:33       ` Junio C Hamano [this message]
2009-02-24  5:42         ` Jeff King
2009-02-24  6:59           ` Junio C Hamano
2009-02-24  7:07             ` Jeff King

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=7v8wnxun8e.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=eletuchy@facebook.com \
    --cc=eletuchy@gmail.com \
    --cc=eugene@facebook.com \
    --cc=git@vger.kernel.org \
    --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).