From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Steve Sakoman <steve@sakoman.com>
Cc: Martin Jansa <martin.jansa@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [langdale][PATCH 2/2] externalsrc.bbclass: Remove a trailing slash from ${B}
Date: Sat, 5 Nov 2022 19:46:43 +0000 [thread overview]
Message-ID: <b9edf078b81a42d9b64ad375a29d3018@axis.com> (raw)
In-Reply-To: <CAOSpxdbOxC-Vgzbw-dtj_TpiEGXo1kL6jeN-8L9TjCgrJy_4xQ@mail.gmail.com>
> -----Original Message-----
> From: Steve Sakoman <steve@sakoman.com>
> Sent: den 5 november 2022 20:41
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: Martin Jansa <martin.jansa@gmail.com>; openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [langdale][PATCH 2/2] externalsrc.bbclass: Remove a trailing slash from ${B}
>
> On Sat, Nov 5, 2022 at 9:36 AM Peter Kjellerstedt <peter.kjellerstedt@axis.com> wrote:
> >
> > Argh, the second series (with three patches) is intended for Kirkstone,
> > not Langdale.
>
> No worries! I think we are good in kirkstone too:
>
> https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-nut
>
> Patch series for both will go out for review in the next day or so
> once autobuilder testing is done.
>
> Steve
Ok, good. Since I typically work with the poky repository, I do not
normally see the *-nut branches, and tend to forget they exist in
another repository.
//Peter
next prev parent reply other threads:[~2022-11-05 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 15:42 [langdale][PATCH 1/2] externalsrc.bbclass: fix git repo detection Peter Kjellerstedt
2022-11-05 15:42 ` [langdale][PATCH 2/2] externalsrc.bbclass: Remove a trailing slash from ${B} Peter Kjellerstedt
2022-11-05 17:59 ` [OE-core] " Steve Sakoman
2022-11-05 18:28 ` Martin Jansa
2022-11-05 19:36 ` Peter Kjellerstedt
2022-11-05 19:40 ` Steve Sakoman
2022-11-05 19:46 ` Peter Kjellerstedt [this message]
2022-11-05 19:52 ` Steve Sakoman
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=b9edf078b81a42d9b64ad375a29d3018@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.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 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.