From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tcpreplay: cross-compile with tcpdump support
Date: Mon, 27 Jan 2014 15:26:21 +0100 [thread overview]
Message-ID: <8761p5zek2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAFOYHZA-wWx2ET2ibXNukvVX0rrsnK85H7+X+YR9oD=0WqNm1A@mail.gmail.com> (Chris Packham's message of "Fri, 24 Jan 2014 11:47:46 +1300")
>>>>> "Chris" == Chris Packham <judge.packham@gmail.com> writes:
Hi,
>> > So i think this patch will work.
>>
>> Ups, you're right - Sorry.
>>
>> Committed patch, thanks.
>>
> Thanks. I was about to say the same thing.
> On the build error front are we concerned about the failures? I
> haven't heard anything from upstream yet. We probably want to move to
> tcpreplay 4.0.2 before the buildroot 2014.02 release.
Yes, I got tired of the autobuilder issues, so I've added your patch
from the pull request.
A patch to bump the version would be good as well, thank.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-01-27 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 10:41 [Buildroot] [PATCH 1/1] Fixed tcpreplay auto build errors Martin Bark
2014-01-22 3:07 ` Chris Packham
2014-01-22 8:58 ` Peter Korsgaard
2014-01-23 0:54 ` Chris Packham
2014-01-23 7:37 ` Peter Korsgaard
2014-01-23 9:07 ` [Buildroot] [PATCH] tcpreplay: cross-compile with tcpdump support Chris Packham
2014-01-23 11:30 ` Peter Korsgaard
2014-01-23 20:08 ` Martin Bark
2014-01-23 21:31 ` Peter Korsgaard
2014-01-23 22:47 ` Chris Packham
2014-01-27 14:26 ` Peter Korsgaard [this message]
2014-01-28 9:37 ` [Buildroot] [PATCH] tcpreplay: Bump version to 4.0.2 Chris Packham
2014-01-28 10:28 ` Peter Korsgaard
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=8761p5zek2.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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