From: Gerald Combs <gerald@wireshark.org>
To: Developer support list for Wireshark
<wireshark-dev@wireshark.org>,
Graham Bloice <graham.bloice@trihedral.com>
Cc: Emily Shaffer <emilyshaffer@google.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [Wireshark-dev] Joint project with Git for outreachy
Date: Mon, 21 Sep 2020 15:07:49 -0700 [thread overview]
Message-ID: <21f2fdb9-33e0-064c-985e-6dc8692aca61@wireshark.org> (raw)
In-Reply-To: <CALcKHKoE2BCZEuW7rmsCdY4LSyvnCTBDLmgifND7TH+v5ma-6w@mail.gmail.com>
On 9/21/20 9:06 AM, Graham Bloice wrote:
>
> There's also the Wireshark Developers Guide (https://www.wireshark.org/docs/wsdg_html_chunked/) and for those that are sleep deprived there are a selection of talks on dissectors from previous SharkFest conferences, e.g. Writing a Wireshark dissector: https://www.youtube.com/watch?v=Fp_7g5as1VY
>
> and the much more entertaining one with a different approach from Richard here: https://www.youtube.com/watch?v=XFFkC4PdCbI
Speaking of SharkFest, the next one is in a few weeks: https://sharkfestvirtual.wireshark.org/. Along with the sessions listed in the Agenda we'll have a Developer Den open throughout the conference.
next prev parent reply other threads:[~2020-09-21 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 22:21 Joint project with Git for outreachy Jonathan Nieder
2020-09-19 9:12 ` ronnie sahlberg
2020-09-19 19:55 ` brian m. carlson
2020-09-19 22:36 ` Junio C Hamano
2020-09-20 16:17 ` Emily Shaffer
2020-09-21 11:33 ` ronnie sahlberg
2020-09-21 15:24 ` [Wireshark-dev] " Richard Sharpe
[not found] ` <CALcKHKoE2BCZEuW7rmsCdY4LSyvnCTBDLmgifND7TH+v5ma-6w@mail.gmail.com>
2020-09-21 22:07 ` Gerald Combs [this message]
2020-09-19 16:17 ` Richard Sharpe
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21f2fdb9-33e0-064c-985e-6dc8692aca61@wireshark.org \
--to=gerald@wireshark.org \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=graham.bloice@trihedral.com \
--cc=jrnieder@gmail.com \
--cc=sandals@crustytoothpaste.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).