From: Carlos O'Donell <carlos@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>, libc-alpha@sourceware.org
Cc: rth@redhat.com
Subject: Re: Ping Re: Make Alpha <sys/user.h> self-contained
Date: Fri, 11 Nov 2016 19:41:00 -0000 [thread overview]
Message-ID: <d6af037e-8712-6668-1766-80916f4f669e@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611111501570.30336@digraph.polyomino.org.uk>
On 11/11/2016 10:02 AM, Joseph Myers wrote:
> Ping. This patch
> <https://sourceware.org/ml/libc-alpha/2016-11/msg00182.html> is pending
> review.
>
You don't need review for this?
https://sourceware.org/glibc/wiki/Consensus#Trivial_Bug-Fix_Changes
~~~
Anyone can commit a change adding missing #include directives where
it is clear what the right header is for functionality used in a
source file. Post the patch and ChangeLog to libc-alpha with a
short message and then push the commit.
~~~
LGTM.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2016-11-11 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 16:47 Joseph Myers
2016-11-11 15:02 ` Ping " Joseph Myers
2016-11-11 19:41 ` Carlos O'Donell [this message]
2016-11-11 21:08 ` Joseph Myers
2016-11-16 18:13 ` Ping^2 " Joseph Myers
2016-11-17 8:25 ` Richard Henderson
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=d6af037e-8712-6668-1766-80916f4f669e@redhat.com \
--to=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=rth@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).