bug#14545: date --iso-8601 should use colon in time zone offset

2013-06-04 Thread Paul Eggert
On 06/02/2013 09:13 PM, Jordon Kalilich wrote: The output mostly follows the ISO 8601:2004 extended format but fails to include a colon in the time zone offset, as required by section 4.3.2 Complete representations and section 4.3.3 Representations other than complete. If memory serves the

bug#14545: date --iso-8601 should use colon in time zone offset

2013-06-04 Thread Jordon Kalilich
Thus spake Paul Eggert on 06/04/2013 12:10 AM: At any rate, the --iso-8601 option has been deprecated since 2005. Why is it deprecated? I don't recall seeing it in the man page until recently, and I've noticed an increase in the use of ISO 8601 over the past few years. This option seems like it

bug#14545: date --iso-8601 should use colon in time zone offset

2013-06-04 Thread Jim Meyering
Paul Eggert wrote: On 06/02/2013 09:13 PM, Jordon Kalilich wrote: The output mostly follows the ISO 8601:2004 extended format but fails to include a colon in the time zone offset, as required by section 4.3.2 Complete representations and section 4.3.3 Representations other than complete.

bug#14545: date --iso-8601 should use colon in time zone offset

2013-06-04 Thread Eric Blake
On 06/04/2013 09:55 AM, Jordon Kalilich wrote: Thus spake Paul Eggert on 06/04/2013 12:10 AM: At any rate, the --iso-8601 option has been deprecated since 2005. Why is it deprecated? I don't recall seeing it in the man page until recently, and I've noticed an increase in the use of ISO 8601

bug#14555: Facing Some problem in uniq command

2013-06-04 Thread Shahid Hussain
I have a file (named 'a')which contains following data. ; 8003 8004 8005 8010 9040 9041 9042 8336 8336 8337 8338 8338 8339 8340 8341 9000 9216 9217 9218 9219 9220 9221 9232 9233 9234 9248 9249 9250 9251 9264 9265 9280 9296 9281 9297 9001 9226 9040 9040 15008 9041 9042 15009 15010 6169 6170 18000

bug#14555: Facing Some problem in uniq command

2013-06-04 Thread Pádraig Brady
On 06/04/2013 01:07 PM, Shahid Hussain wrote: I have a file (named 'a')which contains following data. ; 8003 8004 8005 8010 9040 9041 9042 8336 8336 8337 8338 8338 8339 8340 8341 9000 9216 9217 9218 9219 9220 9221 9232 9233 9234 9248 9249 9250 9251 9264 9265 9280

bug#14555: Facing Some problem in uniq command

2013-06-04 Thread Eric Blake
tag 14555 moreinfo thanks On 06/04/2013 06:07 AM, Shahid Hussain wrote: I have a file (named 'a')which contains following data. 9041 9042 8336 ... 9041 Ouch. Your file is not sorted. Therefore, 9041 is NOT unique when run through 'uniq', which only compares adjacent lines. And Below

bug#14556: suggestion for 'ls' coreutil, comma'd filesizes in -l output

2013-06-04 Thread Pádraig Brady
On 06/04/2013 09:20 PM, Eric Blake wrote: [adding the list back in the loop; also adding bug-coreutils to get a bug number assigned for 2 doc bugs, and slightly reformatting to avoid excessive top-posting] On 06/04/2013 01:44 PM, smu johnson wrote: I did reply on purpose to you, but only

bug#14555: Facing Some problem in uniq command

2013-06-04 Thread Shahid Hussain
Hi, Appreciate your quick reply. What exactly i m doing is there are so many files in my product which contains some data in name = value format. By using some pattern i m extracting only value field from all files and redirecting the output to one temporarily file as i do not want any value to