From: lsworkemail112 at gmail.com (Luke SanAntonio)
Subject: [PATCH] Added code to output the age as seconds instead of "0 min."
Date: Mon, 1 Oct 2012 21:46:32 -0400 [thread overview]
Message-ID: <CA+g5j+1sfX7SOsMjxMa2Xf-+sdSNOBnhqPG58RDXi297LromkQ@mail.gmail.com> (raw)
In-Reply-To: <50693456.1080201@hupie.com>
At this point it might be best if we just drop the patch... There is no reason
to keep it around if everyone seems to be having doubts and questions...
I am starting to have doubts myself, and there really isn't any reason to keep
it around, other than looks... Sorry for the trouble -- Luke
On Mon, Oct 1, 2012 at 2:12 AM, Ferry Huberts <mailings at hupie.com> wrote:
>
>
> On 30-09-12 23:33, Jason A. Donenfeld wrote:
>>
>> So much confusion. I'll reexplain:
>>
>> Before:
>> You visit a page with cache turned on. It says "modified 1 minute
>> ago".. You visit the page again a little later. It says "modified 1
>> minute ago". You don't really notice, because a minute is a longish
>> amount of time.
>>
>> After:
>> You visit a page with cache turned on. It says "modified 7 seconds
>> ago". You visit the page again a little later. It says "modified 7
>> seconds ago". You do notice, because you're more intimately aware of
>> the fact that a minute after seven seconds is more than seven seconds.
>>
>>
>> This is the only concern. A bit silly perhaps.
>>
>
> I don't care about seconds resolution.
> The cache is exactly the reason we should not have seconds resolution
> because it provokes all kinds of confusion (like this discussion)
>
>
> --
> Ferry Huberts
next prev parent reply other threads:[~2012-10-02 1:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 1:39 Maintaining My Own Cgit Tree Jason
2012-09-27 4:22 ` william.bell
2012-09-27 9:00 ` Tobias.Bieniek
2012-09-27 15:53 ` webmaster
2012-09-29 0:30 ` [PATCH] Added code to output the age as seconds instead of "0 min." lsworkemail112
2012-09-29 5:20 ` Jason
2012-09-29 18:43 ` lsworkemail112
2012-09-29 18:51 ` Jason
2012-09-29 19:14 ` lsworkemail112
2012-09-29 19:15 ` Jason
2012-09-29 19:17 ` lsworkemail112
2012-09-29 19:16 ` lsworkemail112
2012-09-30 5:51 ` mailings
2012-09-30 17:28 ` lsworkemail112
2012-09-30 17:29 ` Jason
2012-09-30 17:40 ` mailings
2012-09-30 21:06 ` lsworkemail112
2012-09-30 21:33 ` Jason
2012-10-01 6:12 ` mailings
2012-10-02 1:46 ` lsworkemail112 [this message]
2012-10-02 2:04 ` Jason
2012-10-02 2:08 ` lsworkemail112
2012-10-01 13:56 ` webmaster
2012-10-08 16:48 ` [PATCH 1/2] add git config parsing during scan-path jamie.couture
2012-10-08 16:48 ` [PATCH 2/2] update documentation jamie.couture
2012-10-08 21:05 `
2012-10-08 21:18 `
2012-10-08 16:49 ` [PATCH] repolist pagination changes jamie.couture
2012-10-08 21:39 ` Jason
2012-10-08 17:12 ` [PATCH] add tag target to generate ctags jamie.couture
2012-10-08 21:41 ` Jason
2012-10-09 10:56 ` [PATCH] add git config parsing during scan-path jamie.couture
2012-10-09 11:33 ` Jason
2012-10-09 11:15 ` Maintaining My Own Cgit Tree mailings
2012-10-09 11:18 ` Jason
-- strict thread matches above, loose matches on Subject: below --
2012-08-18 20:37 [PATCH] Added code to output the age as seconds instead of "0 min." lsworkemail112
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=CA+g5j+1sfX7SOsMjxMa2Xf-+sdSNOBnhqPG58RDXi297LromkQ@mail.gmail.com \
--to=cgit@lists.zx2c4.com \
/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).