archive mirror
 help / color / mirror / Atom feed
From: Alberto Pianon <>
Subject: [PATCH v2 3/3] upstream source tracing: tests
Date: Fri, 21 Apr 2023 09:11:14 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


as agreed in the last weekly meeting I submit this third patch by just 
sending the link to the commit, since the patch contains some big 
compressed JSON files that would be too large for an email message. From 
reading tests and test data, you may get what is the final goal/result 
of this series of patches.



  parent reply	other threads:[~2023-04-21  7:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21  7:05 [PATCH v2 1/3] upstream source tracing: base process alberto
2023-04-21  7:05 ` [PATCH v2 2/3] upstream source tracing: metadata collection alberto
2023-04-21  7:11 ` Alberto Pianon [this message]
2023-04-21  7:28 ` [bitbake-devel] [PATCH v2 1/3] upstream source tracing: base process Luca Ceresoli
2023-04-21 12:52   ` Alberto Pianon
2023-04-21 13:50     ` Peter Kjellerstedt
2023-04-21 16:15       ` Luca Ceresoli
2023-04-23  6:50         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).