mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] Revert "pv: move to staging"
Date: Fri, 14 Feb 2025 23:38:14 +0100	[thread overview]
Message-ID: <CAH+2xPDA4aDP+hVLWOkiD9+xk3BPL2fibjLaUmy7nS0NbnNqFA@mail.gmail.com> (raw)
In-Reply-To: <20250208144533.148473-2-bruno.thomsen@gmail.com>

Den lør. 8. feb. 2025 kl. 15.45 skrev Bruno Thomsen <bruno.thomsen@gmail.com>:
>
> 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>

> ---
>  rules/pv.in | 8 +-------
>  1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/rules/pv.in b/rules/pv.in
> index b1b0cd9b8..5e94364ec 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.
> --
> 2.48.1
>



  parent reply	other threads:[~2025-02-14 22:38 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 [this message]
2025-02-17  7:24   ` [ptxdist] [APPLIED] " Michael Olbrich
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=CAH+2xPDA4aDP+hVLWOkiD9+xk3BPL2fibjLaUmy7nS0NbnNqFA@mail.gmail.com \
    --to=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