2015-02-03 17:19 GMT+01:00 Paul Eggert :
> Thanks, that looks good; please install.
Done, thanks.
Andreas
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 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
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 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
On Wed, Feb 04, 2015 at 12:25:18AM +0100, Mark Wielaard wrote:
> This sounds a bit like https://bugs.kde.org/show_bug.cgi?id=308427 "s390
> memcheck reports tsearch conditional jump or move depends on
> uninitialized value". But that bug got fixed some time ago and should
> not be in the latest ver
