From: Khem Raj <raj.khem@gmail.com>
To: Alberto Pianon <alberto@pianon.eu>
Cc: bitbake-devel@lists.openembedded.org,
richard.purdie@linuxfoundation.org, jpewhacker@gmail.com,
carlo@piana.eu
Subject: Re: [bitbake-devel] [PATCH] upstream source tracing: data collection (patch 2/3)
Date: Wed, 26 Apr 2023 23:56:27 -0700 [thread overview]
Message-ID: <CAMKF1srdkydixmdbW4dm8egyNYHOxJ5kGoDtTt-WPB_zyWefig@mail.gmail.com> (raw)
In-Reply-To: <afcd01000f265238360efcdaecd16a4e@pianon.eu>
On Wed, Apr 26, 2023 at 10:19 PM Alberto Pianon <alberto@pianon.eu> wrote:
>
> Il 2023-04-27 07:14 Alberto Pianon ha scritto:
> > Could you please check if this is really the case in your case?
> > You'd need to go to meta/recipes-sato/matchbox-panel-2/files
> > (check where the layer is located in your filesystem) and do
>
> Of course it is located at
> /mnt/b/yoe/master/sources/poky/meta/recipes-sato/m
> atchbox-panel-2/files/0001-applets-systray-Allow-icons-to-be-smaller.patch
>
> :)
>
> Please check also the other two files for which you get the warnings
My distro uses git submodules at top level and poky is a submodule see
https://github.com/yoedistro/yoe-distro
git rev-parse --is-inside-work-tree
true
% git status
HEAD detached at 5a944d32a1
nothing to commit, working tree clean
>
> thanks!
>
> Alberto
next prev parent reply other threads:[~2023-04-27 6:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 6:21 [PATCH] upstream source tracing: data collection (patch 2/3) alberto
2023-04-27 3:49 ` [bitbake-devel] " Khem Raj
2023-04-27 5:14 ` Alberto Pianon
2023-04-27 5:18 ` Alberto Pianon
2023-04-27 6:56 ` Khem Raj [this message]
2023-04-27 7:02 ` Alberto Pianon
[not found] ` <1759B8A6082B56AB.32698@lists.openembedded.org>
2023-04-27 14:10 ` Alberto Pianon
2023-04-27 19:40 ` Khem Raj
2023-04-28 7:47 ` Alberto Pianon
2023-04-28 13:47 ` Khem Raj
2023-05-02 10:44 ` Alberto Pianon
2023-05-02 16:41 ` Alberto Pianon
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=CAMKF1srdkydixmdbW4dm8egyNYHOxJ5kGoDtTt-WPB_zyWefig@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=alberto@pianon.eu \
--cc=bitbake-devel@lists.openembedded.org \
--cc=carlo@piana.eu \
--cc=jpewhacker@gmail.com \
--cc=richard.purdie@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).