From: "hongxu" <hongxu.jia@eng.windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] lib: sbom30: Prefix aliases with "http://spdx.org/spdxdocs/"
Date: Fri, 22 Nov 2024 17:57:51 -0800 [thread overview]
Message-ID: <14003.1732327071481281530@lists.openembedded.org> (raw)
In-Reply-To: <20241122201557.2247079-1-JPEWhacker@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
Hi Joshua,
This patch conflicts with '[PATCH V2 1/3] sbom30/spdx30: add link prefix and name to namespace of spdxId and alias '[1],
would you have suggestions about review '[RR V2][NULL][0/3] SPDX 3.0: Reduce redundant spdxid-hash symlinks to save inode on host '[2]?
Should I rebase my review along with your patch?
[1]https://lists.openembedded.org/g/openembedded-core/message/207412?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3ACreated%2C%2C%2C20%2C2%2C0%2C109680229%2Cd%253D4&d=4
[2]https://lists.openembedded.org/g/openembedded-core/topic/109680228#msg207411
//Hongxu
[-- Attachment #2: Type: text/html, Size: 704 bytes --]
prev parent reply other threads:[~2024-11-23 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 20:15 [OE-core][PATCH] lib: sbom30: Prefix aliases with "http://spdx.org/spdxdocs/" Joshua Watt
2024-11-23 1:57 ` hongxu [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=14003.1732327071481281530@lists.openembedded.org \
--to=hongxu.jia@eng.windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.