bug#34345:

2019-02-09 Thread Assaf Gordon
On 2019-02-09 1:18 p.m., Ricky Tigg wrote: Covered object by values '1994 s', '2014.25 s' seems to be a unique time elapsed. Those values can therefore be expected to be identical, either '1994 s' or '2014.25 s' – 2014 s and 25 hundredths of s –. The command was: # dd if=/dev/zero of=/dev/sdc

bug#34345:

2019-02-09 Thread Ricky Tigg
Covered object by values '1994 s', '2014.25 s' seems to be a unique time elapsed. Those values can therefore be expected to be identical, either '1994 s' or '2014.25 s' – 2014 s and 25 hundredths of s –.

bug#34199: closed (Re: bug#34199: Small bug in cp (for win64))

2019-02-09 Thread Chris Kalish
Hi, guys ... any word on this? (see below) -chris On Sun, Jan 27, 2019 at 9:38 PM Chris Kalish wrote: > Hmmm ... not sure of the distribution, but the help file pointed me at > this address: > > C:\> cp --version > > cp (GNU coreutils) 5.3.0 > > Written by Torbjorn Granlund, David MacKenzie, a

bug#34347: At least add 2nd comm error message after output

2019-02-09 Thread Pádraig Brady
On 06/02/19 04:16, 積丹尼 Dan Jacobson wrote: > (info "(coreutils) comm invocation") > > "Before ‘comm’ can be used, the input files must be sorted" > > "If an input file is diagnosed as being unsorted, the ‘comm’ command > will exit with a nonzero st