From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "dl9pf@gmx.de" <dl9pf@gmx.de>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] Fix bitbake-layerindex to checkout the requested branch
Date: Fri, 14 Feb 2020 15:32:07 +0000 [thread overview]
Message-ID: <8650a200f4274ea79ba23e1e6604004c@XBOX03.axis.com> (raw)
In-Reply-To: <20200214150109.29296-1-dl9pf@gmx.de>
> -----Original Message-----
> From: bitbake-devel-bounces@lists.openembedded.org <bitbake-devel-
> bounces@lists.openembedded.org> On Behalf Of dl9pf@gmx.de
> Sent: den 14 februari 2020 16:01
> To: bitbake-devel@lists.openembedded.org
> Subject: [bitbake-devel] [PATCH] Fix bitbake-layerindex to checkout the
> requested branch
>
> From: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
>
> Bitbake-layerindex would not respect the branch given with -b .
> This fixes the clone command.
>
> V2: Corrected 'branch' back to 'branches' and added
> a FIXME on multiple LAYERSERIES_CORENAMES.
> V3: After discussion on IRC use branches[-1] as well
> educated guess for now but leave the FIXME in place.
Information about the various patch revisions should go below the "---"
below as they relate to the patch process and not the commit that
eventually ends up in the Git repository.
> Signed-off-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
> ---
> lib/bblayers/layerindex.py | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
//Peter
next prev parent reply other threads:[~2020-02-14 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 15:01 [PATCH] Fix bitbake-layerindex to checkout the requested branch dl9pf
2020-02-14 15:32 ` Peter Kjellerstedt [this message]
2020-02-14 18:08 ` Mark Hatle
2020-02-14 21:07 ` "Jan-Simon Möller"
-- strict thread matches above, loose matches on Subject: below --
2020-02-14 14:47 dl9pf
2020-02-14 14:22 dl9pf
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=8650a200f4274ea79ba23e1e6604004c@XBOX03.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=dl9pf@gmx.de \
/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.