From: "Clement Faure" <clement.faure@arm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] devtool: avoid recursion into nested git repos with submodules
Date: Thu, 12 Feb 2026 02:06:21 -0800 [thread overview]
Message-ID: <1270865.1770890781039994422@lists.openembedded.org> (raw)
In-Reply-To: <CF2BD347-8BC8-4985-862A-2CD3BCCB716E@arm.com>
On Tue, Feb 10, 2026 at 12:59 PM, Ross Burton wrote:
>
> Hi Clement,
>
> On 4 Feb 2026, at 14:37, Clement Faure via lists.openembedded.org
> <clement.faure=arm.com@lists.openembedded.org> wrote:
> > + if ".gitmodules" in dirs + files:
>
> I’m guessing this was to mirror the code above, but as far as I’m aware
> .gitmodules is always a file and not a directory, so this can just look in
> files, right?
Yes, you're right. I will fix that in v2
>
> Cheers,
> Ross
>
>
next prev parent reply other threads:[~2026-02-12 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 14:37 [PATCH 0/2] devtool: handle nested git repos with submodules Clement Faure
2026-02-04 14:37 ` [PATCH 1/2] devtool: avoid recursion into " Clement Faure
2026-02-10 11:58 ` [OE-core] " Ross Burton
2026-02-12 10:06 ` Clement Faure [this message]
2026-02-04 14:37 ` [PATCH 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=1270865.1770890781039994422@lists.openembedded.org \
--to=clement.faure@arm.com \
--cc=openembedded-core@lists.openembedded.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