Junio C Hamano <gitster@pobox.com> wrote:Raw timestamps would be easiest. But this is for-each-ref, not git-log. Its %(authortime) macro in the --format string does not support any sort of date formatting options. So uh, no, --pretty=format won't help me here. I'd have to make code changes to for-each-ref to allow control of how timestamps are output. Then I'd have to put magic flags into git-gui to see what version of git I'm using and assume if the flag will work or not. And if it won't then I still have to fall back into the current Jan/Feb/Mar code that I have right now. So I'm actually not inclined right now to fix for-each-ref. But I probably should. Its going on my "Git todo pile". Which as everyone on this list knows is currently about 10x what I can actually accomplish in my natural lifetime. ;-) -- Shawn. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Paul Jackson | Re: cpuset-remove-sched-domain-hooks-from-cpusets |
| James Bottomley | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| David Miller | Slow DOWN, please!!! |
| Masami Hiramatsu | Re: [RFC PATCH v4] Unified trace buffer |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Parag Warudkar | Re: 2.6.29-rc3: tg3 dead after resume |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
