mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Markus Heidelberg <m.heidelberg@cab.de>
Subject: Re: [ptxdist] [APPLIED] nodejs_packages: update URL to Yarn SemVer documentation
Date: Sun, 29 Mar 2026 07:46:58 +0200	[thread overview]
Message-ID: <20260329054658.2501342-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <baf128466763bcbe726ce2fb0740b1cc7d203e24.1773667641.git.m.heidelberg@cab.de>

Thanks, applied as 9b156b79a198ad6e7227d0684756f10cbcf43a77.

Michael

[sent from post-receive hook]

On Sun, 29 Mar 2026 07:46:57 +0200, Markus Heidelberg <m.heidelberg@cab.de> wrote:
> Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
> Message-Id: <baf128466763bcbe726ce2fb0740b1cc7d203e24.1773667641.git.m.heidelberg@cab.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/nodejs_packages.in b/rules/nodejs_packages.in
> index aea44205da41..3e57abd46845 100644
> --- a/rules/nodejs_packages.in
> +++ b/rules/nodejs_packages.in
> @@ -37,7 +37,7 @@ config NODEJS_PACKAGES_LIST
>  	  As a prerequisite the path '${PTXDIST_WORKSPACE}/local_src/nodejs_
>  	  packages/' must exist in the BSP *before* building this package.
>  
> -	  [1] https://legacy.yarnpkg.com/en/docs/dependency-versions/
> +	  [1] https://classic.yarnpkg.com/en/docs/dependency-versions
>  
>  config NODEJS_PACKAGES_LICENSE
>  	string



      parent reply	other threads:[~2026-03-29  5:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 13:30 [ptxdist] [PATCH 1/2] " Markus Heidelberg via ptxdist
2026-03-16 13:30 ` [ptxdist] [PATCH 2/2] nodejs_packages: update URL to PTXdist *_LICENSE description Markus Heidelberg via ptxdist
2026-03-29  5:46   ` [ptxdist] [APPLIED] " Michael Olbrich
2026-03-29  5:46 ` 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=20260329054658.2501342-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=m.heidelberg@cab.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