Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Benjamin Gilbert" <bgilbert@backtick.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: master/main branch renaming and bitbake
Date: Thu, 13 May 2021 13:41:30 -0700	[thread overview]
Message-ID: <5132.1620938490195007398@lists.openembedded.org> (raw)
In-Reply-To: <7ebd5f52982311726a6aebd89eba9cae07bdf999.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

On Thu, May 13, 2021 at 01:09 PM, Richard Purdie wrote:

> 
> Some of our users have complained, yes. That isn't a conscious decision on
> 
> "our" part, just a rather unfortunate and unplanned consequence of the
> fact
> we're pretty strict about declaring where we get our sources.
> 
> The advice to anyone hitting this issue is to add in the correct branch
> to the SRC_URI. It is simple and easy to do, can be in bbappends
> or even changed via anonymous python and similar if necessary. We've
> already
> found the issue with several core recipes, we simply updated them and most
> 
> users didn't notice. I would even likely take that kind of change into
> older
> otherwise unmaintained branches and I think I did so in at least one case
> in
> the past.
> 
> There is no intent to peanlize or complain, my intent is just to deal with
> 
> it like any other upstream source change, these things happen all the
> time.
> I am stating that here for any other maintainers to read and suggest they
> follow oe-core's lead.

Whoops, just saw this.  Thanks for the position statement, Richard; very much appreciated.

Best,
--Benjamin Gilbert

[-- Attachment #2: Type: text/html, Size: 1243 bytes --]

  reply	other threads:[~2021-05-13 20:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 20:34 master/main branch renaming and bitbake colin walters
2021-05-12 20:40 ` [OE-core] " Alexander Kanavin
2021-05-12 20:43   ` colin walters
2021-05-12 21:17     ` Alexander Kanavin
2021-05-12 21:22       ` Alexander Kanavin
2021-05-13  0:11         ` Andre McCurdy
2021-05-13  7:08           ` Richard Purdie
2021-05-13 13:27             ` colin walters
2021-05-13 13:36               ` Bruce Ashfield
2021-05-13 19:02                 ` Benjamin Gilbert
2021-05-13 19:03                   ` [OE-core] " Bruce Ashfield
2021-05-13 19:24                     ` Benjamin Gilbert
2021-05-13 19:34                       ` [OE-core] " Bruce Ashfield
2021-05-13 19:36                       ` Alexander Kanavin
2021-05-13 19:44                         ` Konrad Weihmann
2021-05-13 19:54                         ` Benjamin Gilbert
2021-05-13 20:02                           ` [OE-core] " Konrad Weihmann
2021-05-13 20:06                           ` Alexander Kanavin
2021-05-13 20:34                             ` Benjamin Gilbert
2021-05-13 21:04                               ` [OE-core] " Alexander Kanavin
2021-05-13 20:08               ` Richard Purdie
2021-05-13 20:41                 ` Benjamin Gilbert [this message]
2021-05-13 21:33                 ` colin walters
2021-05-13 22:48                   ` Richard Purdie
2021-05-19 16:53                     ` Andre McCurdy
2021-05-13 14:25             ` Peter Kjellerstedt
2021-05-13 20:12               ` Richard Purdie
2021-05-12 20:41 ` Martin Jansa

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=5132.1620938490195007398@lists.openembedded.org \
    --to=bgilbert@backtick.net \
    --cc=openembedded-core@lists.openembedded.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