Git Mailing List Archive on
 help / color / Atom feed
From: Jonathan Nieder <>
To: Amanda Shafack <>
Cc: Emily Shaffer <>,,
	Developer support list for Wireshark 
Subject: Re: Introduction - An Outreachy 2020 Applicant
Date: Thu, 15 Oct 2020 20:05:18 -0700
Message-ID: <> (raw)
In-Reply-To: <>

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

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. 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.



  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
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] <>
     [not found] ` <>
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Mailing List Archive on

Archives are clonable:
	git clone --mirror git/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 git git/ \
	public-inbox-index git

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone