From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Will Newton <will.newton@linaro.org>
Cc: "libc-ports@sourceware.org" <libc-ports@sourceware.org>,
Patch Tracking <patches@linaro.org>, <overseers@sourceware.org>
Subject: Add willnewton to glibc group
Date: Thu, 29 Aug 2013 20:56:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1308292054410.1487@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CANu=DmjuyjpV8KfaSF8BWbC68ix7Oe2cqQfWwcMiyCs5GaubWA@mail.gmail.com>
On Thu, 29 Aug 2013, Will Newton wrote:
> I've filed a bug and posted a v2. I don't have commit access so I'm
> not sure what the best way to facilitate the cherry pick is. Apart
> from the NEWS entry the merge should be trivial.
It's time for you to get commit access to commit your own patches once
they've been approved. Overseers, please add user willnewton to the glibc
group.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-08-29 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 19:17 [PATCH] ARM: Fix clone code when built for Thumb Will Newton
2013-08-29 19:26 ` Joseph S. Myers
2013-08-29 20:19 ` Will Newton
2013-08-29 20:56 ` Joseph S. Myers [this message]
2013-08-30 10:18 ` Will Newton
2013-08-30 17:35 ` Carlos O'Donell
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=Pine.LNX.4.64.1308292054410.1487@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=overseers@sourceware.org \
--cc=patches@linaro.org \
--cc=will.newton@linaro.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).