public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>,
	Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
	Torvald Riegel <triegel@redhat.com>,
	libc-alpha@sourceware.org
Subject: Re: Subsystem maintainers
Date: Thu, 09 Oct 2014 01:30:00 -0000	[thread overview]
Message-ID: <5435E538.8040003@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1410081529250.30476@digraph.polyomino.org.uk>

On 10/08/2014 11:31 AM, Joseph S. Myers wrote:
> On Wed, 8 Oct 2014, Siddhesh Poyarekar wrote:
> 
>> At the expense of overestimating my expertise in various components
>> (and my understanding of the way our development model works), I
>> volunteer to be subsystem maintainer for benchtests (since I wrote it)
>> and nscd (since I spent a fair bit of time fixing netgroups bugs and
>> miscellaneous things).  I can also be fallback for malloc since I
>> spent a fair bit of time in that code for work reasons in the past
>> (tech support debugging other people's memory corruption is fun, for
>> some liberal definitions of fun).
> 
> I support having you as maintainer for benchtests and nscd.  malloc is 
> sufficiently central I think we may be better off having reviewers for it.
> 

I agree. In general for core pieces of glibc we want multiple reviewers.

Cheers,
Carlos.

  reply	other threads:[~2014-10-09  1:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 20:41 soft-fp: Support rsigned == 2 in _FP_TO_INT Joseph S. Myers
2014-09-30 14:40 ` Ping " Joseph S. Myers
2014-09-30 14:47   ` Carlos O'Donell
2014-09-30 17:29     ` Joseph S. Myers
2014-10-07 16:23     ` Subsystem maintainers Joseph S. Myers
2014-10-07 18:07       ` Carlos O'Donell
2014-10-07 19:44         ` Torvald Riegel
2014-10-08  9:49           ` Thomas Schwinge
2014-10-08 10:31             ` Torvald Riegel
2014-10-08 11:45               ` Joseph S. Myers
2014-10-08 23:29               ` Joseph S. Myers
2014-10-17  8:20                 ` Thomas Schwinge
2014-10-17  8:23                   ` Siddhesh Poyarekar
2014-10-17  8:38                   ` Florian Weimer
2014-10-08 11:42             ` Joseph S. Myers
2014-10-08 15:19               ` Siddhesh Poyarekar
2014-10-08 15:31                 ` Joseph S. Myers
2014-10-09  1:30                   ` Carlos O'Donell [this message]
2014-11-04 16:21                   ` Carlos O'Donell
2014-10-08  6:56         ` Siddhesh Poyarekar
2014-10-08  9:40         ` Matthew Fortune
2014-10-13 11:35       ` Joseph S. Myers
2014-10-20 15:31         ` Joseph S. Myers
2014-10-20 18:15           ` Roland McGrath
2014-10-24  0:47             ` Joseph S. Myers
2014-11-04 16:24               ` Siddhesh Poyarekar
2014-11-04 16:38                 ` Joseph Myers
2014-11-04 18:15                   ` Siddhesh Poyarekar
2014-11-04 21:48                     ` Roland McGrath
2014-11-04 22:16                     ` Joseph Myers
2014-10-06 10:03   ` Ping^2 Re: soft-fp: Support rsigned == 2 in _FP_TO_INT Joseph S. Myers
2014-10-09  1:26 ` 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=5435E538.8040003@redhat.com \
    --to=carlos@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@redhat.com \
    --cc=thomas@codesourcery.com \
    --cc=triegel@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).