From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] wireshark: rework and update to wireshark 1.8.7
Date: Thu, 30 Jan 2014 10:01:19 +0100 [thread overview]
Message-ID: <20140130090119.GH9989@pengutronix.de> (raw)
In-Reply-To: <20140127073312.GA20644@omega>
On Mon, Jan 27, 2014 at 08:33:13AM +0100, Alexander Aring wrote:
> Hi Michael,
>
> On Mon, Jun 03, 2013 at 01:53:25PM +0200, Michael Olbrich wrote:
> > On Mon, May 27, 2013 at 01:54:54PM +0200, Alexander Aring wrote:
> > > This patch removes the build of common gtk-interface wireshark.
> > > Instead of the gtk-interface you can use the cli-interface (tshark) to
> > > capture network traffic into 'capture files'.
> > > On the host side, the gtk-wireshark interface can open the capture files
> > > and show the captured packets.
> > >
> > > I let the KConfig name to WIRESHARK, because it is a common name and all
> > > people who wants 'wireshark' on embedded targets mean 'tshark'.
> >
> > That's ok. The package should be named after the source anyways.
> > I haven't tested it yet, but it looks ok so far. I'll come bake to this
> > after the release.
> >
> ping :-)
>
> what's about this? Was there some problems to bake this wireshark cake?
>
> Should I resend and rebase this patches on current master?
It just got lost. I've applied this with a followup update to the latest
version.
Michael
>
> - Alex
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-01-30 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 11:54 Alexander Aring
2013-06-03 11:53 ` Michael Olbrich
2014-01-27 7:33 ` Alexander Aring
2014-01-30 9:01 ` Michael Olbrich [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=20140130090119.GH9989@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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