public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos_odonell at mentor dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/14040] nearbyintl@GLIBC_2.1 missing from libm
Date: Fri, 29 Jun 2012 15:34:00 -0000 [thread overview]
Message-ID: <bug-14040-131-lxqJrOuzrN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14040-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14040
Carlos O'Donell <carlos_odonell at mentor dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #3 from Carlos O'Donell <carlos_odonell at mentor dot com> 2012-06-29 15:33:54 UTC ---
(In reply to comment #2)
> So it may be ready for backporting to 2.15 - but still needs a tested backport
> patch to be provided for review.
>
> Until we have commit messages automatically appearing in bugs mentioned in
> those messages, I think it's the committer's responsibility to update bugs with
> references to relevant commits. (And it's always their responsibility to close
> bugs once fixed on all relevant branches. Carlos, should we add this to the
> end of the committer checklist?)
I've updated the Committer's Checklist to include a section on closing the
relevant bugzilla entry with the appropriate information.
It seems that the intent was to have this issue as the backport request.
Set to waiting, since we are waiting for a tested backport.
--
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-06-29 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 10:40 [Bug math/14040] New: " schwab@linux-m68k.org
2012-06-27 22:34 ` [Bug math/14040] " jsm28 at gcc dot gnu.org
2012-06-29 11:48 ` jsm28 at gcc dot gnu.org
2012-06-29 15:34 ` carlos_odonell at mentor dot com [this message]
2012-12-01 17:06 ` aj at suse dot de
2012-12-01 19:51 ` schwab@linux-m68k.org
2014-06-13 14:07 ` fweimer 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-14040-131-lxqJrOuzrN@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: 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).