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:34:45 -0700 [thread overview]
Message-ID: <18445.1620938085981224859@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj9K2m7ucmPihEzSyjXw7Cno-cnX9jgzP081-VeObbmJmg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
On Thu, May 13, 2021 at 01:07 PM, Alexander Kanavin wrote:
>
> It's not that different from deleting or archiving old tarball downloads -
> yes it keeps things clean and tidy for upstream, but it will break
> someone's automated build that way, no matter how obsolete the code being
> downloaded.
>
Tarballs, commits on published branches, and annotated tags are all supposed to be stable artifacts. But I don't know of any general expectation that a specific branch continues to exist, other than the one created by Bitbake. GitHub's branch rename tool doesn't leave the old branch behind, not even a symref, so I don't think this is a fringe viewpoint. And as I said, automated builds usually only care about tags, commits, and the default branch.
I genuinely appreciate the discussion, all. In the two upstream projects I mentioned, I'm going to recommend that we re-delete the master branches after a reasonable migration period has elapsed.
Best,
--Benjamin Gilbert
[-- Attachment #2: Type: text/html, Size: 1065 bytes --]
next prev parent reply other threads:[~2021-05-13 20:34 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 [this message]
2021-05-13 21:04 ` Alexander Kanavin
2021-05-13 20:08 ` Richard Purdie
2021-05-13 20:41 ` Benjamin Gilbert
2021-05-13 21:33 ` [OE-core] " 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=18445.1620938085981224859@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.