> ray:~/work/home$ date -ud 'jan 1, 1970 + 11 seconds'
> Fri Mar 18 01:58:31 UTC 2005
> ray:~/work/home$ date -ud 'jan 1, 1970 + 11 seconds + 0800'
> Fri Mar 18 09:58:31 UTC 2005
I sent David a short script to do almost that, except that mine needed
to negate the timezone whereas y
On Mon, 2005-04-18 at 15:46 +1000, David Woodhouse wrote:
> Add tool to render git's " " into an RFC2822-compliant
> string, because I don't think date(1) can do it.
I admit it's not obvious, but date(1) includes gnu's full date parser,
so you can pull stunts like:
ray:~/work/home$ date -ud 'jan
On Mon, 2005-04-18 at 12:27 +0200, Petr Baudis wrote:
> Yes. As far as I'm concerned, I'd put such stuff to git log, and extend
> it usage so that it is possible to print individual log entries with it
> - just make it accept a _range_ of commits, and then do
>
> git log $commit $commit
T
Dear diary, on Mon, Apr 18, 2005 at 09:08:24AM CEST, I got a letter
where David Woodhouse <[EMAIL PROTECTED]> told me that...
> On Mon, 2005-04-18 at 07:43 +0100, Sanjoy Mahajan wrote:
> > Is this short script good enough:
>
> It's not far off; thanks. We might as well just do it like that inside
Add tool to render git's " " into an RFC2822-compliant
string, because I don't think date(1) can do it. Use same for 'git log'
output.
Signed-off-by: David Woodhouse <[EMAIL PROTECTED]>
--- Makefile
+++ Makefile2005-04-18 15:40:43.0 +1000
@@ -14,7 +14,7 @@
PROG= update-cache show
5 matches
Mail list logo