From: Joey Salazar <jgsal@protonmail.com>
To: Richard Sharpe <realrichardsharpe@gmail.com>
Cc: Developer support list for Wireshark
<wireshark-dev@wireshark.org>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [Wireshark-dev] [Outreachy] Internship blog 2020 post #3
Date: Thu, 07 Jan 2021 22:10:28 +0000 [thread overview]
Message-ID: <cF5FePFVqe50PlPOkh4100u774XTAelFPO-RjC6ZnmFRHNq_R03ZXYYsUFWjigd-YO48osHZVFz4ebAPM5Mpsfdle_XTVeykS8d43nA35ho=@protonmail.com> (raw)
In-Reply-To: <CACyXjPwv5kWUKEZNxdpk8+9d3KhAzoDsbwqVZFPVxcbg7Y0JRA@mail.gmail.com>
On Thursday, January 7, 2021 11:35 AM, Richard Sharpe wrote:
> On Thu, Jan 7, 2021 at 8:13 AM Joey Salazar via Wireshark-dev
> wireshark-dev@wireshark.org wrote:
>
> > Hi all,
> > A new blog entry talking a bit about both Git and Wireshark here [1].
> > Check it out! Due to Xmas holidays last week, the next post will be there next week (as opposed to the 2-week break in between posts as usual).
>
> Hi Joey,
>
> Is there any code we can look at?
Hi Richard,
No new code as of right now, but the accepted change is in MR !1313 [1] and upcoming changes building on the patch you shared with us for https support are Coming Soon(tm) : )) I'm also working on the other ideas from issue #17093 [2] and I've updated the blog post [3] to mention your pointers and the previous Git Version parsing MR !805 here [4].
I'll share new code asap, very looking forward to your feedback!
--
Joey
[1] gitlab.com/wireshark/wireshark/-/merge_requests/1313
[2] gitlab.com/wireshark/wireshark/-/issues/17093
[3] www.jsal.home.blog/2021/01/06/think-about-your-audience/
[4] gitlab.com/wireshark/wireshark/-/merge_requests/805
prev parent reply other threads:[~2021-01-07 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 3:28 [Outreachy] Internship blog 2020 post #3 Joey Salazar
[not found] ` <CACyXjPwv5kWUKEZNxdpk8+9d3KhAzoDsbwqVZFPVxcbg7Y0JRA@mail.gmail.com>
2021-01-07 22:10 ` Joey Salazar [this message]
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='cF5FePFVqe50PlPOkh4100u774XTAelFPO-RjC6ZnmFRHNq_R03ZXYYsUFWjigd-YO48osHZVFz4ebAPM5Mpsfdle_XTVeykS8d43nA35ho=@protonmail.com' \
--to=jgsal@protonmail.com \
--cc=git@vger.kernel.org \
--cc=realrichardsharpe@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).