From: Junio C Hamano Date: Thu, 16 Aug 2012 23:02:01 GMT Subject: [PATCH 0/2] relative future date Message-ID: <1345158123-22189-1-git-send-email-gitster@pobox.com> In-Reply-To: <1341505087-13632-1-git-send-email-tomxue0126@gmail.com> Jundong Xue writes: > tomxue@ubuntu:~/mycode/life$ git todo > * d768da9 - (in the future: 3 hours later) Meeting with vendor > * 5fcd556 - (in the future: 12 days later) Take my personal ho > * 9dd280b - (in the future: 11 months later) > * 4680099 - (in the future: 9 months later) > * 59d5266 - (in the future: 8 months later) > * b5308da - (in the future: 7 months later) > ... 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 per-se. 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 was an unmaintainable mess. Here is an attempt to clean it up. Opinions? If the list finds this is a worthwhile thing to do (I am neutral), it needs help from i18n people to mark format messages up properly again. Thanks. Junio C Hamano (2): date: refactor the relative date logic from presentation date: show relative dates in the future date.c | 187 +++++++++++++++++++++++++++++++++++++++++++------------- t/t0006-date.sh | 2 + 2 files changed, 146 insertions(+), 43 deletions(-) -- 1.7.12.rc3.69.gaf0166d