public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/11754] RFE: dlopen of ET_EXEC file
Date: Thu, 15 Jan 2015 20:34:00 -0000	[thread overview]
Message-ID: <bug-11754-131-UYHHfEdVTE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11754-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=11754

--- Comment #11 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
See

https://sourceware.org/glibc/wiki/Contribution%20checklist

regarding submitting patches.  This patch doesn't appear to have been 
submitted to libc-alpha in the patchwork era (March 2014 onwards), if at 
all, so it's not visible as a patch pending review (even with patches in 
patchwork, they should still be pinged weekly).

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-01-15 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11754-131@http.sourceware.org/bugzilla/>
2012-02-21  1:49 ` [Bug ld.so|libdl/11754] " jsm28 at gcc dot gnu.org
2013-01-15 16:28 ` [Bug dynamic-link/11754] " schwab@linux-m68k.org
2014-06-30 17:45 ` fweimer at redhat dot com
2015-01-14 21:41 ` gokcen.eraslan at gmail dot com
2015-01-15 20:34 ` joseph at codesourcery dot com [this message]
2015-01-31  1:34 ` bugdal at aerifal dot cx

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-11754-131-UYHHfEdVTE@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).