From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Ninette Adhikari <ninette@neighbourhood.ie>
Cc: engineering@neighbourhood.ie, poky@lists.yoctoproject.org
Subject: Re: [poky] [PATCH 0/3] Improvements for performance test report view
Date: Mon, 15 Apr 2024 12:46:16 +0200 [thread overview]
Message-ID: <CANNYZj9hmATK-hhBBr=s1uFDJdJ+8siPsWsT=nCxRwGg+UKmRA@mail.gmail.com> (raw)
In-Reply-To: <CAG1aeW31Dov+0DAw5NTWcr9Lgm7W+=sTz3C8jy7-CsZvP5ApbQ@mail.gmail.com>
On Mon, 15 Apr 2024 at 12:40, Ninette Adhikari <ninette@neighbourhood.ie> wrote:
> I had the impression that I would have to send poky related patches to the poky mailing list. So sorry for blasting everyone unnecessarily! I will send the patches to the openembedded-core list.
> Thanks for your response.
No need to be sorry, beginner's mistake. You should have a README.md
in the top level poky/ directory that explains which patches should be
going where (and why is it that way).
Alex
prev parent reply other threads:[~2024-04-15 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 15:32 [PATCH 0/3] Improvements for performance test report view Ninette Adhikari
2024-04-12 15:32 ` [PATCH 1/3] oe-build-perf-report: Add apache echarts to make report interactive Ninette Adhikari
2024-04-12 15:33 ` [PATCH 2/3] oe-build-perf-report: Display more than 300 commits and date instead of commit number Ninette Adhikari
2024-04-12 15:33 ` [PATCH 3/3] oe-build-perf-report: Improve report styling and add descriptions Ninette Adhikari
2024-04-15 10:00 ` [poky] [PATCH 0/3] Improvements for performance test report view Alexander Kanavin
2024-04-15 10:40 ` Ninette Adhikari
2024-04-15 10:46 ` Alexander Kanavin [this message]
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='CANNYZj9hmATK-hhBBr=s1uFDJdJ+8siPsWsT=nCxRwGg+UKmRA@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=engineering@neighbourhood.ie \
--cc=ninette@neighbourhood.ie \
--cc=poky@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).