public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/14287] Backport RPC header patch from master
Date: Thu, 30 Jan 2014 20:04:00 -0000 [thread overview]
Message-ID: <bug-14287-131-KAQAhmPCob@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14287-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14287
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|glibc_2.14 |
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #13 from Carlos O'Donell <carlos at redhat dot com> ---
I am not backporting to 2.14.
I have completed the 2.15 backport.
commit d9ba4bd3ea5f4c004d8894120e2613a9518a88d6
Author: Carlos O'Donell <carlos@redhat.com>
Date: Thu Jan 30 15:03:04 2014 -0500
[PATCH] Make sunrpc code usable again
New configure option --enable-obsolete-rpc makes the deprecated RPC
headers and functions available at compile time as they were before
version 2.14. This option will be removed at some time in the future
after the TI-RPC library becomes fully sufficient for the needs of
existing applications.
(cheery pick from commit 82071029502b354886f86e315c230b808d99afc2)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-01-30 20:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 9:25 [Bug build/14287] New: Backport RPC header patch form master sepek at lavabit dot com
2012-06-24 9:31 ` [Bug build/14287] Backport RPC header patch from master sepek at lavabit dot com
2012-06-24 16:35 ` carlos_odonell at mentor dot com
2012-06-27 22:43 ` jsm28 at gcc dot gnu.org
2012-06-30 8:00 ` sepek at lavabit dot com
2012-06-30 8:01 ` sepek at lavabit dot com
2012-06-30 8:02 ` sepek at lavabit dot com
2012-06-30 8:04 ` sepek at lavabit dot com
2012-06-30 14:33 ` carlos_odonell at mentor dot com
2012-06-30 14:38 ` carlos_odonell at mentor dot com
2012-06-30 14:41 ` joseph at codesourcery dot com
2012-07-01 9:17 ` sepek at lavabit dot com
2012-07-01 9:19 ` sepek at lavabit dot com
2012-07-01 9:24 ` sepek at lavabit dot com
2012-12-03 23:59 ` carlos at systemhalted dot org
2014-01-30 20:04 ` carlos at redhat dot com [this message]
2014-06-13 15:00 ` 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-14287-131-KAQAhmPCob@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).