From: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
To: ceph-devel@vger.kernel.org
Cc: Sage Weil <sage@inktank.com>
Subject: Re: [PATCH 0/2] two small patches for CEPH wireshark plugin
Date: Thu, 24 Jan 2013 21:49:05 +0100 [thread overview]
Message-ID: <51019E41.9070705@bisect.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1301241028420.13935@cobra.newdream.net>
Am 24.01.2013 19:31, schrieb Sage Weil:
> Hi Danny!
[...]
> Since you brought up wireshark...
>
> We would LOVE LOVE LOVE it if this plugin could get upstream into
> wireshark.
Yes, this would be great.
> IIRC, the problem (last time we checked, ages ago) was that
> there were strict coding guidelines for that project that weren't
> followed. I'm not sure if that is still the case, or even if that is
> accurate.
>
> It would be great if someone on this list who is looking for a way to
> contribute could take the lead on trying to make this happen... :-)
I'll take a look at it maybe ... if I find some free time for it.
What about the patches? Can we apply them to the ceph git tree until we
have another solution for the wireshark code?
Danny
next prev parent reply other threads:[~2013-01-24 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 17:21 [PATCH 0/2] two small patches for CEPH wireshark plugin Danny Al-Gaaf
2013-01-24 17:21 ` [PATCH 1/2] wireshark: fix guint64 print format handling Danny Al-Gaaf
2013-01-24 17:21 ` [PATCH 2/2] wireshark: fix indention Danny Al-Gaaf
2013-01-24 18:31 ` [PATCH 0/2] two small patches for CEPH wireshark plugin Sage Weil
2013-01-24 20:49 ` Danny Al-Gaaf [this message]
2013-01-24 20:57 ` Sage Weil
2013-01-29 4:35 ` David Zafman
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=51019E41.9070705@bisect.de \
--to=danny.al-gaaf@bisect.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.