Well, I was just miffed that one can do
$ while cp -u ...
which in some situations will never stop.
J> why stop at one second? The MS-DOS FAT filesystem has a two-second
J> granularity
Ah, no wonder. Ok, --granularity=2...
___
Bug-findutils mailing li
James Youngman <[EMAIL PROTECTED]> writes:
> If the timestamps are different, they're different. After all, why
> stop at one second? The MS-DOS FAT filesystem has a two-second
> granularity and I don't hear people clamouring to have a feature where
> the time values for tools are computed &(~1)
On Thu, Jun 09, 2005 at 03:18:03AM +0800, Dan Jacobson wrote:
> Perhaps add a flag to cp, find, etc. to reduce time comparisons to
> only one second granularity, as depending on the device mounted, or if
> we have since rebooted, times that should be the same can be reported
> back differently by t
Perhaps add a flag to cp, find, etc. to reduce time comparisons to
only one second granularity, as depending on the device mounted, or if
we have since rebooted, times that should be the same can be reported
back differently by the operating system.
Or at least add a warning on man and Info pages.
