public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Clement Faure <clement.faure@arm.com>
To: openembedded-core@lists.openembedded.org
Cc: saul.wold@windriver.com, ross.burton@arm.com,
	Clement Faure <clement.faure@arm.com>
Subject: [PATCH v2 0/2] devtool: handle nested git repos with submodules
Date: Thu, 12 Feb 2026 11:38:01 +0100	[thread overview]
Message-ID: <20260212103803.63277-1-clement.faure@arm.com> (raw)

This patch set fixes devtool modify command when a recipe fetches a
git repository with submodules to BB_GIT_DEFAULT_DESTSUFFIX.
Devtool would parse BB_GIT_DEFAULT_DESTSUFFIX recursively and
attempt a duplicate git submodule add command resulting in a
devtool modify command failure.
The patch fixes that and stops descending once .gitmodules is
detected.
A selftest test case has been added to cover this scenario.

Tests ran:
- devtool.*

changes in v2:
- fix patch 1

Clement Faure (2):
  devtool: avoid recursion into nested git repos with submodules
  oeqa/selftest/devtool: add devtool modify testcase for nested gitsm

 .../devtool/devtool-test-git-gitsm_git.bb     | 10 ++++++++
 meta/lib/oeqa/selftest/cases/devtool.py       | 25 +++++++++++++++++++
 scripts/lib/devtool/__init__.py               |  4 +++
 3 files changed, 39 insertions(+)
 create mode 100644 meta-selftest/recipes-test/devtool/devtool-test-git-gitsm_git.bb

-- 
2.43.0



             reply	other threads:[~2026-02-12 10:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 10:38 Clement Faure [this message]
2026-02-12 10:38 ` [PATCH v2 1/2] devtool: avoid recursion into nested git repos with submodules Clement Faure
2026-02-12 10:38 ` [PATCH v2 2/2] oeqa/selftest/devtool: add devtool modify testcase for nested gitsm Clement Faure

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=20260212103803.63277-1-clement.faure@arm.com \
    --to=clement.faure@arm.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.com \
    --cc=saul.wold@windriver.com \
    /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