From: Kevin Jones <k.j.jonez@gmail.com>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Wireshark
Date: Thu, 04 Jul 2013 17:15:29 +0100 [thread overview]
Message-ID: <51D59FA1.5010306@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1306271245320.397@cobra.newdream.net>
Hi Sage,
I tried sending a patch for this but think it probably bounced due to
size so have opened a pull request instead,
https://github.com/ceph/ceph/pull/396. Needs more work of course but a
starting point.
Regards
Kev
prev parent reply other threads:[~2013-07-04 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 10:22 Wireshark Kevin Jones
2013-06-27 12:33 ` Wireshark Sage Weil
[not found] ` <51CC801F.30303@gmail.com>
[not found] ` <alpine.DEB.2.00.1306271245320.397@cobra.newdream.net>
2013-07-04 16:15 ` Kevin Jones [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51D59FA1.5010306@gmail.com \
--to=k.j.jonez@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
/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