From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] tcpdump: Version bump. 4.99.2 -> 4.99.3
Date: Wed, 8 Feb 2023 12:49:46 +0100 [thread overview]
Message-ID: <20230208114946.2009309-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230114210413.2687213-2-christian.melki@t2data.com>
Thanks, applied as dffaf44e3980a5dec1cfc9d0d6b4c24d906c97b7.
Michael
[sent from post-receive hook]
On Wed, 08 Feb 2023 12:49:46 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Very minor changes.
> Unusual for the tcpdump gang to do so small releases
> with very little time apart the two.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230114210413.2687213-2-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/tcpdump.make b/rules/tcpdump.make
> index 4a040e01704f..594ecea28ac0 100644
> --- a/rules/tcpdump.make
> +++ b/rules/tcpdump.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_TCPDUMP) += tcpdump
> #
> # Paths and names
> #
> -TCPDUMP_VERSION := 4.99.2
> -TCPDUMP_MD5 := 69f8cc8e44606ba49482fa98c2f7f937
> +TCPDUMP_VERSION := 4.99.3
> +TCPDUMP_MD5 := 491aeb15c1c72d59b9288a5a6953e8a9
> TCPDUMP := tcpdump-$(TCPDUMP_VERSION)
> TCPDUMP_SUFFIX := tar.gz
> TCPDUMP_URL := http://www.tcpdump.org/release/$(TCPDUMP).$(TCPDUMP_SUFFIX)
next prev parent reply other threads:[~2023-02-08 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 21:04 [ptxdist] [PATCH] libpcap: Version bump. 1.10.2 -> 1.10.3 Christian Melki
2023-01-14 21:04 ` [ptxdist] [PATCH] tcpdump: Version bump. 4.99.2 -> 4.99.3 Christian Melki
2023-02-08 11:49 ` Michael Olbrich [this message]
2023-02-08 11:49 ` [ptxdist] [APPLIED] libpcap: Version bump. 1.10.2 -> 1.10.3 Michael Olbrich
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=20230208114946.2009309-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--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