From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] neatvnc: version bump 0.8.1 -> 0.9.3
Date: Fri, 7 Mar 2025 10:49:50 +0100 [thread overview]
Message-ID: <20250307094950.4097124-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250226120622.2797629-2-p.zabel@pengutronix.de>
Thanks, applied as 70e619c2e6495aae53c914c57687a6581f9c9ec5.
Michael
[sent from post-receive hook]
On Fri, 07 Mar 2025 10:49:50 +0100, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> https://github.com/any1/neatvnc/releases/tag/v0.9.0
> https://github.com/any1/neatvnc/releases/tag/v0.9.1
> https://github.com/any1/neatvnc/releases/tag/v0.9.2
> https://github.com/any1/neatvnc/releases/tag/v0.9.3
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Message-Id: <20250226120622.2797629-2-p.zabel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/neatvnc.make b/rules/neatvnc.make
> index af4ba140baae..1fff93d1f0b2 100644
> --- a/rules/neatvnc.make
> +++ b/rules/neatvnc.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_NEATVNC) += neatvnc
> #
> # Paths and names
> #
> -NEATVNC_VERSION := 0.8.1
> -NEATVNC_MD5 := 8192c54b0435a9b6bcf7aa8e580dfb20
> +NEATVNC_VERSION := 0.9.3
> +NEATVNC_MD5 := 7c079be798256004b96c6f53b61d146f
> NEATVNC := neatvnc-$(NEATVNC_VERSION)
> NEATVNC_SUFFIX := tar.gz
> NEATVNC_URL := https://github.com/any1/neatvnc/archive/refs/tags/v$(NEATVNC_VERSION).$(NEATVNC_SUFFIX)
next prev parent reply other threads:[~2025-03-07 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 12:06 [ptxdist] [PATCH 1/2] weston: support neatvnc 0.9 Philipp Zabel
2025-02-26 12:06 ` [ptxdist] [PATCH 2/2] neatvnc: version bump 0.8.1 -> 0.9.3 Philipp Zabel
2025-03-07 9:49 ` Michael Olbrich [this message]
2025-03-07 9:49 ` [ptxdist] [APPLIED] weston: support neatvnc 0.9 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=20250307094950.4097124-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--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