public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: overseers@sourceware.org
Cc: Jakub Jelinek <jakub@redhat.com>,
	jsm28@gcc.gnu.org, Andreas Schwab <schwab@suse.de>
Subject: Glibc write access
Date: Wed, 20 Feb 2019 14:09:00 -0000	[thread overview]
Message-ID: <a1adc5e0-a44e-a506-8bb9-bf4db8622234@suse.cz> (raw)

Overseers,

Please add me marxin to the glibc group after verifying with Jakub, Joseph or Andreas.

Jakub, Joseph or Andreas vouches for my sanity and competence.

I truly understand FSF copyright protocols, and always respect per-branch policies on what I am allowed to touch and how.

Thank you,

Martin Liška

             reply	other threads:[~2019-02-20 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 14:09 Martin Liška [this message]
2019-02-20 14:28 ` Martin Liška
  -- strict thread matches above, loose matches on Subject: below --
2015-01-06 11:44 Richard Earnshaw
2015-01-06 11:58 ` Marcus Shawcroft
2015-01-06 13:37 ` Ian Lance Taylor
2015-01-06 14:16   ` 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=a1adc5e0-a44e-a506-8bb9-bf4db8622234@suse.cz \
    --to=mliska@suse.cz \
    --cc=jakub@redhat.com \
    --cc=jsm28@gcc.gnu.org \
    --cc=overseers@sourceware.org \
    --cc=schwab@suse.de \
    /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).