plain, 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 stateme
ed, I'm going to recommend that we re-delete the master branches after a
reasonable migration period has elapsed.
Best,
--Benjamin Gilbert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#151727):
https://lists.openembedded.org/g/op
and never delete it again or you'll break our builds". See
https://github.com/ostreedev/ostree/issues/2360 and
https://github.com/coreos/go-systemd/issues/371 for examples.
Best,
--Benjamin Gilbert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply
e 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.
--Benjamin Gilber
versus no longer making them the default. Which is penalizing the
> existing users.
Deleting the branch penalizes existing developers, which projects might be
willing to do. Git branch names don't usually have any effect on users.
--Benjamin Gilbert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You rece
