On 04/02/15 18:44, Bruce Korb wrote:
> True. It was mostly a plea for some (findable) documentation.
> In truth, my most common usage is more like:
>
> touch -t $(date --date@$(( $(stat -c %Y file1) + 10 ))
> +%Y%m%d%H%M.%S ) file2
Note +%Y%m%d%H%M.%S is ambiguous on distributed systems (no
True. It was mostly a plea for some (findable) documentation.
In truth, my most common usage is more like:
touch -t $(date --date@$(( $(stat -c %Y file1) + 10 ))
+%Y%m%d%H%M.%S ) file2
Still, I use such constructs rarely enough that I don't know what's reasonable.
An example for use in "touc
On Wed, Feb 4, 2015 at 9:25 AM, Bruce Korb wrote:
> On 02/02/15 09:27, Pádraig Brady wrote:
>>
>> On 02/02/15 16:41, Chris Lamb wrote:
>>>
>>> We are currently in a funny situation where GNU date can't parse its own
>>> output:
>>>
>>>$ date --date="$(date)"
>>>date: invalid date 'Mon 2 F
On 02/02/15 09:27, Pádraig Brady wrote:
On 02/02/15 16:41, Chris Lamb wrote:
We are currently in a funny situation where GNU date can't parse its own
output:
$ date --date="$(date)"
date: invalid date ‘Mon 2 Feb 16:37:46 GMT 2015’
I don't think this will work as the output from date(1
On 02/02/15 16:41, Chris Lamb wrote:
> We are currently in a funny situation where GNU date can't parse its own
> output:
>
> $ date --date="$(date)"
> date: invalid date ‘Mon 2 Feb 16:37:46 GMT 2015’
>
> This is not aesthetically pleasing at the very least.
>
> Signed-off-by: Chris Lamb
>
++--
1 file changed, 17 insertions(+), 2 deletions(-)
--
Chris Lamb
@lolamby / chris-lamb.co.uk
From cd10931b5ff3bd2d0deb9eab5b85b46eccd8acbd Mon Sep 17 00:00:00 2001
From: Chris Lamb
Date: Mon, 2 Feb 2015 16:38:59 +
Subject: [PATCH] lib/parse-datetime.y: Add ability to parse output
