git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emily Shaffer <emilyshaffer@google.com>
To: Richard Sharpe <realrichardsharpe@gmail.com>
Cc: Developer support list for Wireshark 
	<wireshark-dev@wireshark.org>,
	Amanda Shafack <shafack.likhene@gmail.com>,
	git@vger.kernel.org
Subject: Re: [Wireshark-dev] Introduction - An Outreachy 2020 Applicant
Date: Fri, 9 Oct 2020 12:00:09 -0700	[thread overview]
Message-ID: <20201009190009.GO331156@google.com> (raw)
In-Reply-To: <CACyXjPxwmEzJ412CSeQdx=CwXExoZg64nKTkW8AP3rg=OBKEQw@mail.gmail.com>

On Fri, Oct 09, 2020 at 10:46:30AM -0700, Richard Sharpe wrote:
> 
> On Fri, Oct 9, 2020 at 8:18 AM Jonathan Nieder <jrnieder@gmail.com> wrote:
> >
> > Jonathan Nieder wrote:
> >
> > > +wireshark-dev@wireshark.org
> > > Hi Amanda,
> > >
> > > Amanda Shafack wrote:
> > >
> > >> I am Amanda Shafack, an Outreachy 2020 applicant who wishes to
> > >> contribute to the "Add Git protocol support to Wireshark" project.
> 
> Perhaps Amanda could resend her introduction on the wireshark-dev
> mailing list because this is the list for development type questions
> and will get better responses for developer-type questions.

I'm a little confused - did you mean a different list than
wireshark-dev? I think Jonathan did cc the wireshark-dev list.

 - Emily

  reply	other threads:[~2020-10-09 19:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 19:11 Introduction - An Outreachy 2020 Applicant Amanda Shafack
2020-10-09  0:25 ` Jonathan Nieder
2020-10-09  1:43   ` Jonathan Nieder
2020-10-09 17:46     ` [Wireshark-dev] " Richard Sharpe
2020-10-09 19:00       ` Emily Shaffer [this message]
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

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

  git send-email \
    --in-reply-to=20201009190009.GO331156@google.com \
    --to=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=realrichardsharpe@gmail.com \
    --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.
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 NNTP newsgroup(s).