From: Ross Burton <Ross.Burton@arm.com>
To: Clement Faure <Clement.Faure@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/2] devtool: avoid recursion into nested git repos with submodules
Date: Tue, 10 Feb 2026 11:58:27 +0000 [thread overview]
Message-ID: <CF2BD347-8BC8-4985-862A-2CD3BCCB716E@arm.com> (raw)
In-Reply-To: <20260204143732.94832-2-clement.faure@arm.com>
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?
Cheers,
Ross
next prev parent reply other threads:[~2026-02-10 11:59 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 ` Ross Burton [this message]
2026-02-12 10:06 ` Clement Faure
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=CF2BD347-8BC8-4985-862A-2CD3BCCB716E@arm.com \
--to=ross.burton@arm.com \
--cc=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