From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Upstream <mptcp@lists.linux.dev>
Subject: MPTCP: new blog
Date: Tue, 13 Feb 2024 15:48:58 +0100 [thread overview]
Message-ID: <6f47121a-da23-4647-bd2c-5b42aa14b05c@kernel.org> (raw)
Hello,
Last month, I started a new blog about my work that is now sponsored by
NGI0 Core [1]. Now that the second post is online, I just realised I
forgot to mention this blog here, on the mailing list :)
So here we go:
https://blog.mptcp.dev
Of course, opinions shared through this blog are my own and not the
views of the whole MPTCP Community or my sponsor ;)
[1] https://nlnet.nl/project/MPTCP-deployability/
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
reply other threads:[~2024-02-13 14:49 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=6f47121a-da23-4647-bd2c-5b42aa14b05c@kernel.org \
--to=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
/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