Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <adrian.freihofer@siemens.com>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH v3 1/4] dev-manual/devtool: fix non-patch local file handling docs
Date: Fri, 16 Oct 2026 14:32:10 +0200	[thread overview]
Message-ID: <DM69JPLMA50U.3VATVP3WUMFK5@bootlin.com> (raw)
In-Reply-To: <20261015200726.2391599-2-adrian.freihofer@siemens.com>

On Thu Oct 15, 2026 at 10:06 PM CEST, Adrian Freihofer via lists.yoctoproject.org wrote:
> From: Adrian Freihofer <adrian.freihofer@siemens.com>
>
> Non-patch ``file://`` entries in :term:`SRC_URI` no longer end up in an
> ``oe-local-files`` folder: that mechanism, along with ``S = WORKDIR``, was
> removed in 5.1 (see migration-5.1.rst). Whether such files reach
[...]

Applied to master-next, thanks!

Make sure to rebase on master-next, as there are some conflicts applying your
patches there.

Antonin


  reply	other threads:[~2026-10-16 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 20:06 [PATCH v3 0/4] dev-manual/devtool: ide-sdk doc rewrite and Mermaid diagrams AdrianF
2026-10-15 20:06 ` [PATCH v3 1/4] dev-manual/devtool: fix non-patch local file handling docs AdrianF
2026-10-16 12:32   ` Antonin Godard [this message]
2026-10-15 20:06 ` [PATCH v3 2/4] dev-manual/devtool: update devtool ide-sdk section for recent features AdrianF
2026-10-16 12:32   ` [docs] " Antonin Godard
2026-10-15 20:06 ` [PATCH v3 3/4] dev-manual/devtool: add diagrams for the ide-sdk workflow and architecture AdrianF
2026-10-16 12:32   ` [docs] " Antonin Godard
     [not found] ` <20261015200726.2391599-5-adrian.freihofer@siemens.com>
2026-10-16 12:32   ` [docs] [PATCH v3 4/4] dev-manual/devtool: convert add/modify/upgrade flow diagrams to Mermaid Antonin Godard

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=DM69JPLMA50U.3VATVP3WUMFK5@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=docs@lists.yoctoproject.org \
    /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