public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/866] glob should match dangling symlinks Date: Tue, 08 May 2012 16:43:00 -0000 [thread overview] Message-ID: <bug-866-131-vKfW18F2rq@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-866-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=866 Rich Felker <bugdal at aerifal dot cx> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |bugdal at aerifal dot cx Resolution|INVALID | --- Comment #5 from Rich Felker <bugdal at aerifal dot cx> 2012-05-08 16:43:12 UTC --- This seems like yet another unexplained/unreasonable bug closure by Drepper. Can we please get a serious review of it. I think the fact that glob() is behaving differently from bash, and the fact that one expects "rm *" to remove everything including dangling symlinks, speaks for itself; POSIX does not have any special language about symlinks in the specification for glob, so by default I think it requires them to be included in the results. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-05-08 16:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-866-131@http.sourceware.org/bugzilla/> 2012-05-08 11:25 ` pmatilai at laiskiainen dot org 2012-05-08 11:51 ` joseph at codesourcery dot com 2012-05-08 16:43 ` bugdal at aerifal dot cx [this message] 2012-05-15 9:06 ` mjw at redhat dot com 2012-09-27 4:43 ` glibc at tomlee dot co 2015-08-27 22:02 ` [Bug glob/866] " jsm28 at gcc dot gnu.org 2005-04-22 19:50 [Bug libc/866] New: " splite-glibc at sigint dot cs dot purdue dot edu 2005-04-22 19:54 ` [Bug libc/866] " splite-glibc at sigint dot cs dot purdue dot edu 2005-09-27 5:54 ` drepper at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-866-131-vKfW18F2rq@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).