From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] Revert "pv: move to staging"
Date: Mon, 17 Feb 2025 08:24:48 +0100 [thread overview]
Message-ID: <20250217072448.53437-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250208144533.148473-2-bruno.thomsen@gmail.com>
Thanks, applied as 629c2365037f7aff5f45f6851762f9b80229657c.
Michael
[sent from post-receive hook]
On Mon, 17 Feb 2025 08:24:48 +0100, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> Package has been updated to latest upstream release from 2025-01-28.
>
> This reverts commit 91986bc436945d3e1697c7685e50ecfa6a24c377.
>
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Message-Id: <20250208144533.148473-2-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/pv.in b/rules/pv.in
> index b1b0cd9b8a43..5e94364ec72b 100644
> --- a/rules/pv.in
> +++ b/rules/pv.in
> @@ -1,6 +1,4 @@
> -## SECTION=staging
> -## old section:
> -### SECTION=shell_and_console
> +## SECTION=shell_and_console
>
> config PV
> tristate
> @@ -13,7 +11,3 @@ config PV
> quickly data is passing through, how long it has taken, how near to
> completion it is, and an estimate of how long it will be until
> completion.
> -
> - STAGING: remove in PTXdist 2026.03.0
> - Unmaintained in PTXdist, fails to build with current toolchains.
> - Needs updating to the latest version.
next prev parent reply other threads:[~2025-02-17 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 14:45 [ptxdist] [PATCH 1/2] pv: version bump 1.4.12 -> 1.9.31 Bruno Thomsen
2025-02-08 14:45 ` [ptxdist] [PATCH 2/2] Revert "pv: move to staging" Bruno Thomsen
2025-02-14 9:54 ` Michael Olbrich
2025-02-14 22:38 ` Bruno Thomsen
2025-02-17 7:24 ` Michael Olbrich [this message]
2025-02-17 7:24 ` [ptxdist] [APPLIED] pv: version bump 1.4.12 -> 1.9.31 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=20250217072448.53437-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=bruno.thomsen@gmail.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