From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wopr.sciops.net ([216.126.196.60]) by ur; Wed Feb 10 16:08:05 EST 2016 Received: (qmail 24705 invoked by uid 1001); 10 Feb 2016 21:08:03 -0000 Date: Wed, 10 Feb 2016 16:08:03 -0500 From: Kurt H Maier To: 9front@9front.org Subject: Re: [9front] syslog(2) change Message-ID: <20160210210803.GF1886@wopr.sciops.net> Mail-Followup-To: 9front@9front.org References: <1270b9585a3e327733049d87e8a08103@utsuho.znet> <50a1e90923c69e7c710766ab431c23a8@utsuho.znet> <1455120937435-0fca18ba-a33032ef-afc32a2e@stanleylieber.com> <68c8b9c471a28126f0ca4ddfb1f8f034@utsuho.znet> <5b700121babb21f8e721550f9815085f@ghost.attlocal.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: extension-based persistence plugin On Wed, Feb 10, 2016 at 09:57:36PM +0100, Julius Schmidt wrote: > I do much prefer something like yyyy-mm-dd... over burnzez' suggestion. If you're going to put timezones in the logfiles, you pretty much have to use ISO-8601 date formats, and resolve to stick to numeric offsets. As we're discovering on irc, trying to convert from abbreviations to meaningul data is a fool's game. Switching to YYYY-MM-DDTHH:MM:SS+HH:MM is the only sane option. khm