On Thu, 13 May 2021 at 21:25, Benjamin Gilbert <[email protected]> wrote:
> Deleting the branch normally affects people who are in the project's > developer community and pay attention to its announcements. Those folks > can then simply update their local checkouts and move on with their lives. > Everyone else just clones the default branch and maybe checks out a > particular tag or commit before building a package. That workflow still > works after the default branch is renamed. Bitbake's additional checks are > unusual, and impose a long-term compatibility constraint on upstream > projects that they didn't sign up for. > They're not useless though. As a layer maintainer I absolutely want those checks, as I want to be aware of any branch configuration changes upstream, and to ensure I'm not accepting a change in source revision that points to an unattached commit, or one from a branch that's not supposed to be used at all. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#151720): https://lists.openembedded.org/g/openembedded-core/message/151720 Mute This Topic: https://lists.openembedded.org/mt/82782995/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
