From: Joey Salazar <jgsal@protonmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>,
"wireshark-dev@wireshark.org" <wireshark-dev@wireshark.org>
Subject: [Outreachy] Internship blog 2020
Date: Thu, 03 Dec 2020 02:50:12 +0000 [thread overview]
Message-ID: <I55UpoMB_QMpFuqJEp1cHW7oN8AJy-b5iveBe2kZLslum_LOctwR5IdXUJhzZETg7bZDtm4beN38Nz6kvpJKDf0luxBMFxfpoFCYWkwaae4=@protonmail.com> (raw)
Hi all,
Very happy to be joining for this winter's internship! A short blog entry on the beginning of this journey here jsal.home.blog
A new entry every 2 weeks, check it out!
Thank you Outreachy, Git, and Wireshark for the opportunity, happy to be working together!
--
Joey
next reply other threads:[~2020-12-03 2:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 2:50 Joey Salazar [this message]
2020-12-04 2:47 ` [Outreachy] Internship blog 2020 Jonathan Nieder
2020-12-04 3:28 ` [Wireshark-dev] " ronnie sahlberg
2020-12-04 3:33 ` ronnie sahlberg
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='I55UpoMB_QMpFuqJEp1cHW7oN8AJy-b5iveBe2kZLslum_LOctwR5IdXUJhzZETg7bZDtm4beN38Nz6kvpJKDf0luxBMFxfpoFCYWkwaae4=@protonmail.com' \
--to=jgsal@protonmail.com \
--cc=git@vger.kernel.org \
--cc=wireshark-dev@wireshark.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 NNTP newsgroup(s).