|
From: | Eric Blake |
Subject: | Re: [coreutils] Re: [PATCH 2/2] stat: print timestamps to full resolution |
Date: | Thu, 21 Oct 2010 07:52:52 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Mnenhy/0.8.3 Thunderbird/3.1.4 |
On 10/21/2010 03:22 AM, Andreas Schwab wrote:
Jim Meyering<address@hidden> writes:And besides, with coreutils-8.6 already released, reverting the change is no longer an option.Why? I'm pretty sure more breakage will pop up over time.
How would you propose 'fixing' it? By burning three more % specifiers, which are already coming close to a scarce resource? (Note that %W is completely new with coreutils 8.6, so no one has ever had a short %W to deal with, so it is just %[XYZ]). And why give the user less information than what is available? %X was first implemented prior to POSIX 2008, back when subsecond resolution was not mandatory; but now that POSIX requires nanosecond information (even if the file system itself has less granularity), I see no reason to hide that fact, even if a few scripts need to be adjusted to be more robust to potential nanosecond information.
-- Eric Blake address@hidden +1-801-349-2682 Libvirt virtualization library http://libvirt.org
[Prev in Thread] | Current Thread | [Next in Thread] |