From: "duep.fnst@fujitsu.com" <duep.fnst@fujitsu.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][PATCH V1] xz: add ptest support
Date: Thu, 01 Jun 2023 23:34:47 -0700 [thread overview]
Message-ID: <26137.1685687687489513056@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj94YtwNShEtaBQU==pOobdGvU7ohH10GOz_Sis5f6hzDA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 241 bytes --]
Sorry, the second email was accidentally sent by mistake.
Now I have submitted the patch to xz upstream.
But in xz upstream, I submitted the patch via email and it doesn't has the link.
Could I submit the patch email as attachment here?
[-- Attachment #2: Type: text/html, Size: 254 bytes --]
next prev parent reply other threads:[~2023-06-02 6:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 8:34 [meta-oe][PATCH V1] xz: add ptest support duep.fnst
2023-06-01 12:27 ` [OE-core] " Alexander Kanavin
2023-06-02 6:34 ` duep.fnst [this message]
2023-06-02 6:36 ` Alexander Kanavin
2023-06-02 8:18 ` duep.fnst
2023-06-02 8:40 ` [OE-core] " Alexander Kanavin
2023-06-15 7:59 ` duep.fnst
2023-06-15 8:31 ` duep.fnst
2023-06-01 8:52 duep.fnst
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=26137.1685687687489513056@lists.openembedded.org \
--to=duep.fnst@fujitsu.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;
as well as URLs for NNTP newsgroup(s).