From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: overseers@sourceware.org
Cc: thomas@codesourcery.com, joseph@codesourcery.com, roland@frob.com
Subject: Re: glibc group
Date: Tue, 07 Feb 2012 10:22:00 -0000 [thread overview]
Message-ID: <20120207.192233.488203737.kkojima@rr.iij4u.or.jp> (raw)
In-Reply-To: <874nv3nfu7.fsf@schwinge.name>
Thomas Schwinge <thomas@codesourcery.com> wrote:
> Hi!
>
> On Mon, 6 Feb 2012 23:08:13 +0000, "Joseph S. Myers" <joseph@codesourcery.com> wrote:
>> On Tue, 7 Feb 2012, Kaz Kojima wrote:
>>
>> > Looks fine. Thanks for the patch!
>> > Uli, could you please approve the patch in the URL below?
>>
>> You're de facto the SH maintainer in that you review SH patches. I think
>> you should be added to the list at
>> <http://sourceware.org/glibc/wiki/MAINTAINERS> and go in the glibc group
>> to be able to commit patches. (Actually, Thomas should probably go in the
>> group as well for write-after-approval commit of patches as well.)
>
> Thanks; my sourceware login is tschwinge.
>
> I don't know if Kaz has one.
If it's same with the one for sources.redhat.com, my login is kkojima.
Regards,
kaz
next prev parent reply other threads:[~2012-02-07 10:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bopcp5vc.fsf@schwinge.name>
[not found] ` <87sjionqh8.fsf@schwinge.name>
[not found] ` <20120207.072114.282161188.kkojima@rr.iij4u.or.jp>
[not found] ` <Pine.LNX.4.64.1202062305100.1343@digraph.polyomino.org.uk>
2012-02-07 9:39 ` Thomas Schwinge
2012-02-07 10:22 ` Kaz Kojima [this message]
2012-02-08 20:50 ` Roland McGrath
2012-02-08 20:57 ` Joseph S. Myers
2012-02-08 21:01 ` Frank Ch. Eigler
2012-02-10 11:43 ` Thomas Schwinge
2004-07-16 23:15 Ulrich Drepper
2004-07-17 4:44 ` Christopher Faylor
2004-07-17 5:40 ` Alexandre Oliva
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=20120207.192233.488203737.kkojima@rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=joseph@codesourcery.com \
--cc=overseers@sourceware.org \
--cc=roland@frob.com \
--cc=thomas@codesourcery.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).