From: Chris Packham <judge.packham@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tcpreplay: Bump version to 4.0.2
Date: Tue, 28 Jan 2014 22:37:06 +1300 [thread overview]
Message-ID: <1390901826-2954-1-git-send-email-judge.packham@gmail.com> (raw)
In-Reply-To: <8761p5zek2.fsf@dell.be.48ers.dk>
Signed-off-by: Chris Packham <judge.packham@gmail.com>
---
On 28/01/14 03:26, Peter Korsgaard wrote:
>
> A patch to bump the version would be good as well, thank.
>
Here you go. I've heard back from upstream, the maintainer is dealing with some
family issues so the patch from my pull request will do for now. Build tested
with/without BR2_PACKAGE_TCPDUMP.
package/tcpreplay/tcpreplay.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/tcpreplay/tcpreplay.mk b/package/tcpreplay/tcpreplay.mk
index a2cd16e..fdb42a5 100644
--- a/package/tcpreplay/tcpreplay.mk
+++ b/package/tcpreplay/tcpreplay.mk
@@ -4,7 +4,7 @@
#
################################################################################
-TCPREPLAY_VERSION = 4.0.0
+TCPREPLAY_VERSION = 4.0.2
TCPREPLAY_SITE = http://downloads.sourceforge.net/project/tcpreplay/tcpreplay/$(TCPREPLAY_VERSION)
TCPREPLAY_LICENSE = GPLv3
TCPREPLAY_LICENSE_FILES = docs/LICENSE
--
1.8.4.rc2
next prev parent reply other threads:[~2014-01-28 9:37 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
2014-01-28 9:37 ` Chris Packham [this message]
2014-01-28 10:28 ` [Buildroot] [PATCH] tcpreplay: Bump version to 4.0.2 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=1390901826-2954-1-git-send-email-judge.packham@gmail.com \
--to=judge.packham@gmail.com \
--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