From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
Roland McGrath <roland@hack.frob.com>,
"GNU C. Library" <libc-alpha@sourceware.org>,
thomas@codesourcery.com
Subject: Re: I'm already gone
Date: Wed, 12 Jul 2017 00:17:00 -0000 [thread overview]
Message-ID: <20170712001740.6lfgojy45qjmg3un@var.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <5f549257-022b-b522-62b7-aec8e88210b9@redhat.com>
Hello,
Carlos O'Donell, on ven. 07 juil. 2017 11:40:26 -0400, wrote:
> On 07/07/2017 11:06 AM, Joseph Myers wrote:
> > I'd like to nominate Samuel Thibault and Thomas Schwinge, if willing, as
> > Hurd port maintainers (which implies full authority to commit any of the
> > backlogged Hurd-specific changes that clearly cannot affect non-Hurd
> > ports, without waiting for any prior review, at least for now including
> > during release freezes, subject to the usual coding standards and always
> > having the option to request review of a particular patch if that seems
> > useful or the patch possibly controversial). (Committed patches should
> > still be posted to libc-alpha, and of course the community may raise
> > issues post-commit which should then be addressed.)
>
> I second that nomination, it would be great to see Samuel and Thomas bring
> the GNU/Hurd port to the point where it builds on master.
I'll be happy to do it.
I now just need to find the time to do it :)
Samuel
next prev parent reply other threads:[~2017-07-12 0:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 7:21 Roland McGrath
2017-07-07 15:06 ` Joseph Myers
2017-07-07 15:40 ` Carlos O'Donell
2017-07-12 0:17 ` Samuel Thibault [this message]
2017-07-20 19:17 ` Paul Eggert
2017-07-07 20:16 ` Roland McGrath
2017-07-07 15:42 ` Carlos O'Donell
2017-07-07 16:59 ` Paul Eggert
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=20170712001740.6lfgojy45qjmg3un@var.youpi.perso.aquilenet.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=roland@hack.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).