From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: "bkylerussell@gmail.com" <bkylerussell@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "wesley.lindauer@gmail.com" <wesley.lindauer@gmail.com>
Subject: Re: [OE-core] [PATCH 1/1] patch: don't strip GitApplyTree patches
Date: Fri, 10 Apr 2020 03:44:26 +0000 [thread overview]
Message-ID: <bb3e559e1e1042e4a2ef485890acad1f@XBOX03.axis.com> (raw)
In-Reply-To: <20200409044116.27070-2-bkylerussell@gmail.com>
> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of bkylerussell@gmail.com
> Sent: den 9 april 2020 06:41
> To: openembedded-core@lists.openembedded.org
> Cc: wesley.lindauer@gmail.com; Kyle Russell <bkylerussell@gmail.com>
> Subject: [OE-core] [PATCH 1/1] patch: don't strip GitApplyTree patches
You want to change the prefix "patch:" to, e.g., "patch.py:" to
differentiate it from a change to the patch recipe.
//Peter
next prev parent reply other threads:[~2020-04-10 3:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 4:41 [PATCH 0/1] patch: don't strip GitApplyTree patches bkylerussell
2020-04-09 4:41 ` [PATCH 1/1] " bkylerussell
2020-04-09 10:07 ` [OE-core] " Richard Purdie
2020-04-27 20:32 ` bkylerussell
2020-04-30 0:01 ` [PATCH v2 0/1] patch.py: don't apply striplevel to git am command bkylerussell
2020-04-30 0:01 ` [PATCH v2 1/1] " bkylerussell
2020-04-10 3:44 ` Peter Kjellerstedt [this message]
2020-04-09 5:02 ` ✗ patchtest: failure for patch: don't strip GitApplyTree patches Patchwork
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=bb3e559e1e1042e4a2ef485890acad1f@XBOX03.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=bkylerussell@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wesley.lindauer@gmail.com \
/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