From: Junio C Hamano <gitster@pobox.com>
To: Jundong Xue <tomxue0126@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Can show relative date of the commit with future timestamp
Date: Mon, 20 Aug 2012 15:51:04 -0700 [thread overview]
Message-ID: <7vsjbhgotj.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: CA+P7oHtGsBoRGsUzg4qqm7sZJ=+1Jh06Gmj1uw+k0-S9Gk+DXQ@mail.gmail.com
Jundong Xue <tomxue0126@gmail.com> writes:
> tomxue@ubuntu:~/mycode/life$ git todo
> * d768da9 - (in the future: 3 hours later) Meeting with vendor — Tom
> Xue (HEAD, master)
> * 5fcd556 - (in the future: 12 days later) Take my personal holiday — Tom Xue
> * 9dd280b - (in the future: 11 months later) 端午节 — Tom Xue
> * 4680099 - (in the future: 9 months later) 清明节 — Tom Xue
> * 59d5266 - (in the future: 8 months later) 元宵节 — Tom Xue
> * b5308da - (in the future: 7 months later) 除夕 — Tom Xue
> ...
I was re-reading the backlog and after looking at it again, I do not
think what the patch tries to do is a bad thing. There are changes
I want to see _how_ it is done, though.
Especially, the duplication of the exact same logic in the future
and in the past is an unmaintainable mess.
I have queued a replacement in 'pu'.
next prev parent reply other threads:[~2012-08-20 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 16:18 [PATCH] Can show relative date of the commit with future timestamp Tom Xue
2012-07-05 17:26 ` Junio C Hamano
[not found] ` <CA+P7oHuCbeJ5shfL5OVhSypgygzmQwn-RGPD8UvFUFuqnoV9fA@mail.gmail.com>
2012-07-06 8:15 ` Jundong Xue
2012-08-20 22:51 ` Junio C Hamano [this message]
2012-08-21 9:17 ` Jundong Xue
2012-08-16 23:02 ` [PATCH 0/2] relative future date Junio C Hamano
2012-08-16 23:02 ` [PATCH 1/2] date: refactor the relative date logic from presentation Junio C Hamano
2012-08-16 23:02 ` [PATCH 2/2] date: show relative dates in the future Junio C Hamano
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=7vsjbhgotj.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=tomxue0126@gmail.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).