From: Taylor Blau <me@ttaylorr.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>, Git at SFC <git@sfconservancy.org>,
Jeff King <peff@peff.net>, Taylor Blau <me@ttaylorr.com>
Subject: Re: [ANNOUNCE] New Git PLC Member
Date: Fri, 18 Feb 2022 13:58:03 -0500 [thread overview]
Message-ID: <Yg/sO63nhhtAXWvn@nand.local> (raw)
In-Reply-To: <CAP8UFD2XxP9r3PJ4GQjxUbV=E1ASDq1NDgB-h+S=v-bZQ7DYwQ@mail.gmail.com>
On Fri, Feb 18, 2022 at 07:34:12PM +0100, Christian Couder wrote:
> We are happy to announce that Taylor Blau is now on the committee.
> Welcome to him!
Thanks, Christian, and the rest of the PLC for this opportunity. I look
forward to serving on the PLC alongside you, Ævar, and Junio.
On a practical note, it feels like we are somewhat overdue for a "Git +
SFC status update", the last one being back from 2018 in [1]. I'll see
if I can gather some more up-to-date information from Conservancy and
send out an updated status report, hopefully soon.
Thanks,
Taylor
[1]: https://lore.kernel.org/git/20180306231609.GA1632@sigill.intra.peff.net/
prev parent reply other threads:[~2022-02-18 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 18:34 [ANNOUNCE] New Git PLC Member Christian Couder
2022-02-18 18:58 ` Taylor Blau [this message]
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=Yg/sO63nhhtAXWvn@nand.local \
--to=me@ttaylorr.com \
--cc=christian.couder@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 NNTP newsgroup(s).