On 27/10/15 17:29, Pádraig Brady wrote: > On 23/10/15 03:39, Pádraig Brady wrote: >> So there is the possibility of changing the output format >> to conform to the standard. How likely is that to break things? >> One possibility is that file names might be generated with >> `date -Im`, but would even that be likely to break things? >> >> Attached is the change to date(1) to adjust the output format, >> and if this is thought too risky, we can instead just >> augment the info docs with Michael's comment above. > > Pushed to coreutils upstream at > http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v8.24-64-g17bbf6c
I'll push the attached follow up info doc tweak later. cheers, Pádraig.
>From e6457ee5424f9a476529e5cfcacfa041b45600cf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C3=A1draig=20Brady?= <[email protected]> Date: Wed, 28 Oct 2015 13:50:40 +0000 Subject: [PATCH] doc: clarify iso-8601 formats used by ls and du * doc/coreutils.texi (du invocation): Remove 'like' from mentions of ISO-8601 as the components are individually conformant. (ls invocation): Likewise, except for --time-style=iso for recent files, where the MM-DD component is not a valid ISO-8601 timestamp. --- doc/coreutils.texi | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/coreutils.texi b/doc/coreutils.texi index b1ba097..33585cb 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -7498,7 +7498,7 @@ files; if you want output columns to line up, you may need to insert spaces in one of the two formats. @item full-iso -List timestamps in full using ISO 8601 like date, time, and time zone +List timestamps in full using ISO 8601 date, time, and time zone components with nanosecond precision, e.g., @samp{2002-03-30 23:45:56.477817180 -0700}. This style is equivalent to @samp{+%Y-%m-%d %H:%M:%S.%N %z}. @@ -7509,14 +7509,14 @@ explain @command{make}'s behavior, since GNU @command{make} uses the full timestamp to determine whether a file is out of date. @item long-iso -List ISO 8601 like date and time in minutes, e.g., +List ISO 8601 date and time components with minute precision, e.g., @samp{2002-03-30 23:45}. These timestamps are shorter than @samp{full-iso} timestamps, and are usually good enough for everyday work. This style is equivalent to @samp{+%Y-%m-%d %H:%M}. @item iso List ISO 8601 dates for non-recent timestamps (e.g., -@samp{2002-03-30@ }), and ISO 8601 like month, day, hour, and +@samp{2002-03-30@ }), and ISO 8601-like month, day, hour, and minute for recent timestamps (e.g., @samp{03-30 23:45}). These timestamps are uglier than @samp{long-iso} timestamps, but they carry nearly the same information in a smaller space and their brevity helps @@ -11491,13 +11491,13 @@ with @command{date}, @var{format}'s interpretation is affected by the @env{LC_TIME} locale category. @item full-iso -List timestamps in full using ISO 8601 like date, time, and time zone +List timestamps in full using ISO 8601 date, time, and time zone components with nanosecond precision, e.g., @samp{2002-03-30 23:45:56.477817180 -0700}. This style is equivalent to @samp{+%Y-%m-%d %H:%M:%S.%N %z}. @item long-iso -List ISO 8601 like date and time in minutes, e.g., +List ISO 8601 date and time components with minute precision, e.g., @samp{2002-03-30 23:45}. These timestamps are shorter than @samp{full-iso} timestamps, and are usually good enough for everyday work. This style is equivalent to @samp{+%Y-%m-%d %H:%M}. -- 2.5.0
