From: Ondrej Oprala <ondrej.oprala@gmail.com>
To: overseers@sourceware.org
Cc: dodji@redhat.com
Subject: libabigail write request
Date: Mon, 12 Dec 2016 13:30:00 -0000 [thread overview]
Message-ID: <486e9a53-76ed-8275-faee-2414d62277c1@gmail.com> (raw)
Overseers,
Please add meondrej.oprala@gmail.com to the libabigail group after verifying with Dodji Seketeli (in CC).
Dodji will hopefully vouch 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,
Ondrej Oprala
next reply other threads:[~2016-12-12 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 13:30 Ondrej Oprala [this message]
2016-12-12 13:43 ` Dodji Seketeli
2016-12-12 14:55 ` Christopher Faylor
2016-12-12 15:24 ` Ondrej Oprala
2016-12-12 15:42 ` Frank Ch. Eigler
2016-12-12 15:43 ` Ondrej Oprala
2016-12-12 15:46 ` Frank Ch. Eigler
2016-12-12 15:51 ` Ondrej Oprala
2016-12-12 15:02 ` Frank Ch. Eigler
[not found] <36e70697-0ae4-1c94-fb8a-7a5f645974d2@gmail.com>
2016-12-12 13:41 ` Dodji Seketeli
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=486e9a53-76ed-8275-faee-2414d62277c1@gmail.com \
--to=ondrej.oprala@gmail.com \
--cc=dodji@redhat.com \
--cc=overseers@sourceware.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).