From: Jonathan Nieder <jrnieder@gmail.com>
To: Amanda Shafack <shafack.likhene@gmail.com>
Cc: Emily Shaffer <emilyshaffer@google.com>,
git@vger.kernel.org,
Developer support list for Wireshark
<wireshark-dev@wireshark.org>
Subject: Re: Introduction - An Outreachy 2020 Applicant
Date: Thu, 15 Oct 2020 20:05:18 -0700 [thread overview]
Message-ID: <20201016030518.GE539114@google.com> (raw)
In-Reply-To: <CAGxm6oUcxLCqhN0+tSA37xsNUJbjcyj3ahraVdiwxnQn-7qC4g@mail.gmail.com>
Hi Amanda,
Amanda Shafack wrote:
> Also, regarding my initial starter contribution, I chose the
> "micro-project" titled "Avoid pipes in git related commands in test
> scripts" (source https://bit.ly/3iZQcT2).
Thanks, sounds good.
> I plan to complete the micro-project and then move on to more research
> on Git's HTTP protocol and other resources you've pointed out.
>
> Let me know your thoughts on this, thanks.
I think that a good next step after the Git micro-project is to get to
know wireshark --- this would involve building wireshark, finding
something to change, and then changing it.
https://gitlab.com/wireshark/wireshark/-/wikis/Development/ describes
how to download and build wireshark. Then for something to change, I
have a few different ideas:
a. tighten the error handling in epan/dissectors/packet-git.c
(for example, what happens when there are not exactly 4 hexdigits
at the beginning of a pkt-line?). Git's
Documentation/technical/protocol-common.txt describes the pkt-line
format and Documentation/technical/pack-protocol.txt describes the
Git transport dissected by packet-git.
b. add tests for the Git dissector. test/README.test and the page it
links to describe how wireshark's tests work
c. try to parse out the service name and protocol version in
epan/dissectors/packet-git.c. Git's
Documentation/technical/protocol-v2.txt describes where we can find
that information
That would get us more comfortable with the wireshark codebase and
would help prepare for fleshing out a plan for the internship.
Thoughts?
Sincerely,
Jonathan
next prev parent reply other threads:[~2020-10-16 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1602590401.25101.wireshark-dev@wireshark.org>
2020-10-15 8:52 ` Wireshark-dev Digest, Vol 173, Issue 14 Amanda Shafack
2020-10-16 3:05 ` Jonathan Nieder [this message]
[not found] <CAGxm6oU+11zAjM6KBNRv4NUhx69CiaLekJ5ZhOhmQA8ofrAzbA@mail.gmail.com>
[not found] ` <CACyXjPy=322gOBbcKpERvBnYnOsPr1OKeTbQktUGSx0+3SSpPA@mail.gmail.com>
2020-10-13 3:10 ` Introduction - An Outreachy 2020 Applicant Jonathan Nieder
2020-10-08 19:11 Amanda Shafack
2020-10-09 0:25 ` Jonathan Nieder
2020-10-09 1:43 ` Jonathan Nieder
2020-10-09 18:57 ` Emily Shaffer
2020-10-09 19:29 ` Amanda Shafack
2020-10-09 7:47 ` Amanda Shafack
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=20201016030518.GE539114@google.com \
--to=jrnieder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=shafack.likhene@gmail.com \
--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).