From: Joseph Myers <joseph@codesourcery.com>
To: "Étienne Buira" <etienne.buira@gmail.com>
Cc: <libc-stable@sourceware.org>
Subject: Re: [PATCH] x86_64: check for SHARED instead of PIC where sensible
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1612191631280.29301@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20161217152344.19910-1-etienne.buira@gmail.com>
libc-stable is only for cherry-picks to past release branches of changes
that are already on master. Only one of these changes appears to be on
master, in a different form and with H.J. Lu's name on it. You need to
get the other changes on master (via proposing them on libc-alpha) before
proposing cherry-picks to any past release branches.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2016-12-19 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 Étienne Buira
2016-01-01 0:00 ` Joseph Myers [this message]
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=alpine.DEB.2.20.1612191631280.29301@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=etienne.buira@gmail.com \
--cc=libc-stable@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).