From: Marius Storm-Olsen <marius@trolltech.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
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: Tue, 24 Feb 2009 07:35:05 +0100 [thread overview]
Message-ID: <49A39519.3030308@trolltech.com> (raw)
In-Reply-To: <20090224050400.GC4615@coredump.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
Jeff King said the following on 24.02.2009 06:04:
> On Mon, Feb 23, 2009 at 09:09:02AM +0100, Marius Storm-Olsen wrote:
>>> Another option would to give higher resolution in number of
>>> years, like "3.5 years" or even "3.1 years".
>> And using shorter names for the units would be a no-go?
>>
>> "3y 2m ago" <--
>
> Personally I think that looks terrible. But I recognize that it is
> very subjective. The only objective thing I can say is that "m" is
> not a unique prefix of a time unit, due to "minutes". Yes, it is
> obvious if you see the "y" first, but I actually parse the relative
> time backwards in my head and think "2 minutes ago, oh wait, 3
> years, that must be months".
Ok, the standard abbreviation for month is "mo.", so
"3y 2mo. ago"
then? ;-)
--
.marius [@trolltech.com]
'if you know what you're doing, it's not research'
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2009-02-24 6:36 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 [this message]
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=49A39519.3030308@trolltech.com \
--to=marius@trolltech.com \
--cc=eletuchy@facebook.com \
--cc=eletuchy@gmail.com \
--cc=eugene@facebook.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.