All of lore.kernel.org
 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: Sun, 22 Feb 2009 17:44:37 -0800	[thread overview]
Message-ID: <7v7i3ix6yi.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090222230620.GB19011@coredump.intra.peff.net> (Jeff King's message of "Sun, 22 Feb 2009 18:06:20 -0500")

Jeff King <peff@peff.net> writes:

> On Fri, Feb 20, 2009 at 01:23:54PM -0800, eletuchy@gmail.com wrote:
>
>> From: Eugene Letuchy <eugene@facebook.com>
>> 
>> In the context of sizing the git blame time column, it doesn't make a
>> lot of sense to see "12 months ago" next to an exact timestamp +
>> timezone for something 13 months ago. This commit makes commits older
>> than 12 months display the date only, not the time.
>
> I think this is an improvement, though I was thinking of taking it a
> step further:
> ...
> +		/* Otherwise, years. Centuries is probably overkill. */
> +		snprintf(timebuf, sizeof(timebuf), "%lu years ago", (diff + 183) / 365);
> +		return timebuf;
>  	}
>  
>  	if (mode == DATE_LOCAL)
>
>
> but maybe other people actually like seeing the absolute time. I've
> always found it jarring when reading relative times (but part of that
> _was_ because it was so long and exact).

I agree this is an improvement.  It irritated me, too.  And I do not think
this change falls into the category of bad backward incompatibility.

I was hoping somebody would do a "N years M months", though.

  reply	other threads:[~2009-02-23  1:46 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 [this message]
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
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=7v7i3ix6yi.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 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.