From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Developer support list for Wireshark
<wireshark-dev@wireshark.org>,
git@vger.kernel.org, Emily Shaffer <emilyshaffer@google.com>
Subject: Re: Joint project with Git for outreachy
Date: Sat, 19 Sep 2020 19:55:45 +0000 [thread overview]
Message-ID: <20200919195545.GH67496@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAN05THSUN4YToYRqWUxZ0r2=wVxJU0V2iWumx1jjx=eTQ7rAYw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
On 2020-09-19 at 09:12:53, ronnie sahlberg wrote:
> Hi Jonathan,
> Hi Emily
>
> Emily, you want to contribute to wireshark? That is awesome. I think I
> speak for everyone to send a HUGE welcome
> your way and hope your experience working on and with wireshark be excellent!
I think there's been a misunderstanding. I think the proposal was to
have Emily and Jonathan, who are both significant contributors to Git,
doing the mentoring from the Git side, along with someone from the
Wireshark side. I don't think we know yet if anyone will be interested
in working on it, but it seems from the response to be a proposal that
has interest in both projects.
Feel free to correct me if I've misunderstood.
> I think a git dissector would be really awesome.
> We do have a packet-git.c already in wireshark, but looking at it it
> is very barebones (understatement of the year:-)
> but getting a real full blown git protocol implementation would be
> totally awesome.
I agree that a Git dissector would be an awesome addition to Wireshark,
for all the reasons mentioned, and I do hope someone is able to pick it
up. I'd personally find such a feature very useful, and I know some
colleagues who probably would as well.
--
brian m. carlson: Houston, Texas, US
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2020-09-19 19:55 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 [this message]
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
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=20200919195545.GH67496@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=ronniesahlberg@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).