[bug #1212] wishlist: ls sort case insensitive option

Follow-up Comment #9, bug #1212 (project coreutils): http://hotsecretarysex.pornlivenews.com/articles/636683/hot-secretary-in-stocking Hot secretary in stocking http://hotsecretarysex.pornlivenews.com/articles/636682/secretary-sex-video Secretary sex video

Re: Bug in uname

On Mon, 8 Dec 2008, Eric Blake wrote: The information contained in this e-mail may be privileged and/or Sending mail from an account that adds a disclaimer longer than the body of your message is considered poor netiquette. This disclaimer is unenforceable on a publicly archived mailing

RE: Bug in uname

Thanks for maintaining a less-than-glorious, but useful utility. I did check to make sure I was getting the expected version of uname: which uname /bin/uname , but attempting to repeat the symptom got proper behavior!??: uname -a Linux cloudy

date(1): -d argument parsing error

Hi. date(1) command parses next $day_of_week_today (where $day_of_week_today is today's day name) incorrectly: $ date Tue Dec 9 17:16:50 GMT 2008 $ date -d next `date +%A` Tue Dec 9 00:00:00 GMT 2008 It should print the next Tuesday's date, i.e. today + 7 days. Cheers, Jan.

Re: date(1): -d argument parsing error

On Tue, Dec 9, 2008 at 5:19 PM, Jan Minář [EMAIL PROTECTED] wrote: Hi. date(1) command parses next $day_of_week_today (where $day_of_week_today is today's day name) incorrectly: $ date Tue Dec 9 17:16:50 GMT 2008 $ date -d next `date +%A` Tue Dec 9 00:00:00 GMT 2008 It should print

rm: option -I and --interactive=once are not behaving equivalently

Hi, Regarding to the manpage and comments in rm.c, the option -I of rm is meant to be the same as --interactive=once It isn't, since when removing a write-protected file, rm prompts if --interactive=once is given, but it doesn't prompt, if -I is given. This behaviour of rm -I is surprising,

Re: date(1): -d argument parsing error

2008/12/10 James Youngman [EMAIL PROTECTED]: $ date -d next `LC_ALL=C date +%A` mercredi 10 décembre 2008, 00:00:00 (UTC+) ^^^ You've just demonstrated that the bug is present in the French localization as well -- the you got is *today*, not *next* Wednesday, as it should

split() command

Dear Sir, why does split() command has different options in different UniX systems? i.e. -a option does not work on some Unix machines... Is this because of long option and short option difference? Thanks, YB ___ Bug-coreutils mailing list

Re: split() command

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Yongsheng Bai on 12/9/2008 8:38 PM: Dear Sir, why does split() command has different options in different UniX systems? i.e. -a option does not work on some Unix machines... Your example of 'split -a' is required by POSIX, so it

Re: split() command

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [please keep replies on the list, and don't top-post] According to Yongsheng Bai on 12/9/2008 8:51 PM: Thanks, Sir. But, how can I fix this problem? - split: invalid option -- d Try `split --help' for more information. split: