From: Paul Eggleton <bluelightning@bluelightning.org>
To: Jon Mason <jdmason@kudzu.us>,
yocto@lists.yoctoproject.org,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>
Cc: Paul Barker <paul.barker@sancloud.com>
Subject: Re: [yocto] Inclusive Language Proposal for YP/OE
Date: Wed, 26 Jan 2022 14:51:18 +1300 [thread overview]
Message-ID: <7338313.EvYhyI6sBW@linc> (raw)
In-Reply-To: <bac12863-a9d7-6fbe-e45b-09cace7dc7fb@sancloud.com>
On Tuesday, 25 January 2022 21:26:33 NZDT Paul Barker wrote:
> The layer index may need some modification to handle different layers
> having different names for the in-development branch. We could implement
> the layer index changes first to support other layers which rename their
> master branch.
>
> I'm going to bite the bullet with meta-linux-mainline and rename the
> master branch to "dev" this week to see what happens.
The layer index does already support this, it's just not exposed (at the time
I introduced it - some time ago - I thought it might encourage people to
deviate from the release branch names, but in hindsight that was probably not
worth worrying about.) So at the moment an admin can set an alternative branch
name. It would not be hard to expose it through the UI for layer maintainers
though.
Cheers,
Paul
next prev parent reply other threads:[~2022-01-26 1:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 16:17 Inclusive Language Proposal for YP/OE Jon Mason
2022-01-25 8:26 ` Paul Barker
2022-01-26 1:51 ` Paul Eggleton [this message]
2022-01-25 15:50 ` [OE-core] " Chuck Wolber
2022-01-25 16:00 ` [oe] " Ross Burton
2022-01-25 16:30 ` [oe] " Ross Burton
2022-01-26 8:37 ` Mikko.Rapeli
2022-01-25 23:07 ` [OE-core] " Randy MacLeod
2022-01-29 3:30 ` [oe] " Peter Kjellerstedt
2022-02-04 13:21 ` [OE-core] " Enrico Scholz
2022-02-04 13:58 ` [oe] " Alexander Kanavin
2022-02-04 14:16 ` Enrico Scholz
2022-02-04 15:01 ` Bryan Evenson
2022-02-04 18:38 ` Enrico Scholz
2022-02-04 19:12 ` Alexander Kanavin
2022-02-04 20:08 ` Enrico Scholz
2022-02-21 8:21 ` [oe] " Marta Rybczynska
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=7338313.EvYhyI6sBW@linc \
--to=bluelightning@bluelightning.org \
--cc=jdmason@kudzu.us \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.barker@sancloud.com \
--cc=yocto@lists.yoctoproject.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).