public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug manual/10672] qsort may not be a stable sort under memory exhaustion
Date: Tue, 01 Jul 2014 08:11:00 -0000 [thread overview]
Message-ID: <bug-10672-131-nffgaIhH9J@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10672-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=10672
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
--- Comment #5 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Anders Kaseorg from comment #4)
> Created attachment 7665 [details]
> Remove incorrect claim from manual
Could you post this patch to the mailing list for review, please?
I think it is best to remove the problematic wording altogether, not attempting
to describe the past behavior of the implementation.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-01 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10672-131@http.sourceware.org/bugzilla/>
2011-10-23 8:17 ` bugdal at aerifal dot cx
2012-12-19 10:47 ` schwab@linux-m68k.org
2014-03-11 7:07 ` allachan at au1 dot ibm.com
2014-07-01 6:49 ` fweimer at redhat dot com
2014-07-01 7:05 ` andersk at mit dot edu
2014-07-01 8:11 ` fweimer at redhat dot com [this message]
2014-07-01 8:15 ` andersk at mit dot edu
2014-12-10 15:50 ` neleai at seznam dot cz
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-10672-131-nffgaIhH9J@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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: link
Be 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).