From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] minicom: Version bump. 2.11 -> 2.11.1
Date: Mon, 9 Mar 2026 08:22:25 +0100 [thread overview]
Message-ID: <20260309072225.4088314-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260303183855.3824395-1-christian.melki@t2data.com>
Thanks, applied as f053a63f11758e5a1fb8b3bffa64ccb7da42e0fd.
Michael
[sent from post-receive hook]
On Mon, 09 Mar 2026 08:22:25 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Minor change for build error. (BOTHER flag, baudrate other, arbitrary).
> https://salsa.debian.org/minicom-team/minicom/-/releases/2.11.1
>
> * Forward patchset. Applies cleanly.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260303183855.3824395-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/minicom-2.11/0001-build-reproducibly.patch b/patches/minicom-2.11.1/0001-build-reproducibly.patch
> similarity index 100%
> rename from patches/minicom-2.11/0001-build-reproducibly.patch
> rename to patches/minicom-2.11.1/0001-build-reproducibly.patch
> diff --git a/patches/minicom-2.11/series b/patches/minicom-2.11.1/series
> similarity index 100%
> rename from patches/minicom-2.11/series
> rename to patches/minicom-2.11.1/series
> diff --git a/rules/minicom.make b/rules/minicom.make
> index b94dd4725e37..6e5bfd2f250d 100644
> --- a/rules/minicom.make
> +++ b/rules/minicom.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_MINICOM) += minicom
> #
> # Paths and names
> #
> -MINICOM_VERSION := 2.11
> -MINICOM_MD5 := bf34ca28ccaccef3883dbbc1ef12275a
> +MINICOM_VERSION := 2.11.1
> +MINICOM_MD5 := c25f65a4b9b1671d92146c6616b5e446
> MINICOM_SUFFIX := tar.bz2
> MINICOM := minicom-$(MINICOM_VERSION)
> MINICOM_URL := https://salsa.debian.org/minicom-team/minicom/-/archive/$(MINICOM_VERSION)/$(MINICOM).$(MINICOM_SUFFIX)
prev parent reply other threads:[~2026-03-09 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 18:38 [ptxdist] [PATCH] " Christian Melki
2026-03-09 7:22 ` 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=20260309072225.4088314-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