mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] batctl: Version bump. 2026.0 -> 2026.3
Date: Tue,  6 Oct 2026 09:01:41 +0200	[thread overview]
Message-ID: <20261006070141.2793389-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20261001174012.3882888-1-christian.melki@t2data.com>

Thanks, applied as 1bdaa5775848fb92a5499224c835c2d72ce75d82.

Michael

[sent from post-receive hook]

On Tue, 06 Oct 2026 09:01:41 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> More fixes the last quarter than the previous 5 years combined.
> Mostly fixes.
> https://git.open-mesh.org/batctl.git/log/?h=v2026.3
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20261001174012.3882888-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/batctl.make b/rules/batctl.make
> index c56779036152..639d72c48f0c 100644
> --- a/rules/batctl.make
> +++ b/rules/batctl.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_BATCTL) += batctl
>  #
>  # Paths and names
>  #
> -BATCTL_VERSION		:= 2026.0
> -BATCTL_SHA256		:= b4b70dae620106e45ee3ddb1f512f69075692b12343d0521267403cb212a4a26
> +BATCTL_VERSION		:= 2026.3
> +BATCTL_SHA256		:= 2c8443fae7b3471a500837f8cfbbc2b7bbab602e43ce8c61b100560dec1d9ee0
>  BATCTL			:= batctl-$(BATCTL_VERSION)
>  BATCTL_SUFFIX		:= tar.gz
>  BATCTL_URL		:= https://downloads.open-mesh.org/batman/stable/sources/batctl/$(BATCTL).$(BATCTL_SUFFIX)



      reply	other threads:[~2026-10-06  7:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 17:40 [ptxdist] [PATCH] " Christian Melki
2026-10-06  7: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=20261006070141.2793389-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