From: Chuck Wolber <chuckwolber@gmail.com>
To: Jon Mason <jdmason@kudzu.us>
Cc: yocto <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>
Subject: Re: [OE-core] Inclusive Language Proposal for YP/OE
Date: Tue, 25 Jan 2022 07:50:33 -0800 [thread overview]
Message-ID: <CAB=6tBSszdZEjyKPvMd88HFKZiszcVuGEt4BH6w8YsS0Ew=gNA@mail.gmail.com> (raw)
In-Reply-To: <CAPoiz9wL16OTzxNHdw_5-L72GOHkhhM0--WZF7An071cx6sr_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
On Mon, Jan 24, 2022 at 8:18 AM Jon Mason <jdmason@kudzu.us> wrote:
%< SNIP %<
> Branch Names
> The “master” branches on the relevant OpenEmbedded and Yocto Project
> git trees will be changed to an alternative name at some point in the
> future. The current preferred name is “devel”.
>
Why devel instead of main [1]?
[1]
https://lore.kernel.org/git/pull.656.v4.git.1593009996.gitgitgadget@gmail.com/
..Ch:W..
--
*"Perfection must be reached by degrees; she requires the slow hand of
time." - Voltaire*
[-- Attachment #2: Type: text/html, Size: 1170 bytes --]
next prev parent reply other threads:[~2022-01-25 15:50 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 ` [yocto] " Paul Eggleton
2022-01-25 15:50 ` Chuck Wolber [this message]
2022-01-25 16:00 ` [oe] [OE-core] " 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='CAB=6tBSszdZEjyKPvMd88HFKZiszcVuGEt4BH6w8YsS0Ew=gNA@mail.gmail.com' \
--to=chuckwolber@gmail.com \
--cc=jdmason@kudzu.us \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--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).