From: David Edelsohn <dje.gcc@gmail.com>
To: GCC Development <gcc@gcc.gnu.org>,
Binutils Development <binutils@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>,
gdb@sourceware.org
Cc: Elena Zannoni <ezannoni@gmail.com>
Subject: Apology to Dr. Elena Zannoni
Date: Thu, 29 Dec 2022 12:06:27 -0500 [thread overview]
Message-ID: <CAGWvnymr93Cn5uaHeGxk6CqqjeyCeoNqJXQKD2V280gvDWwg0g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
At GNU Cauldron 2022 during the GNU Toolchain Infrastructure BoF session I
displayed inappropriate and uncharacteristic behavior towards Dr. Elena
Zannoni. Because I realized that my behavior was inappropriate, I
proactively apologized to Dr. Zannoni during a conversation immediately
after the BoFs. She graciously accepted my apology and responded
that everything was okay.
I wish to reiterate my apology publicly to her. I am sorry if the incident
might have caused anyone discomfort at the event, or about GNU Cauldron or
the GNU Toolchain community. I will be more careful in the future.
Happy Holidays and Happy New Year,
David
reply other threads:[~2022-12-29 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAGWvnymr93Cn5uaHeGxk6CqqjeyCeoNqJXQKD2V280gvDWwg0g@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=binutils@sourceware.org \
--cc=ezannoni@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@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).