From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: Colin Walters <walters@verbum.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] master/main branch renaming and bitbake
Date: Wed, 12 May 2021 23:17:30 +0200 [thread overview]
Message-ID: <CANNYZj-PSq4bAQpy3s=8Vuqk-PcstZZFPzr710VXfS3Lj8Aiow@mail.gmail.com> (raw)
In-Reply-To: <255c6c61-af04-4866-bb2f-0ddc50ca6391@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On Wed, 12 May 2021 at 22:44, Colin Walters <walters@verbum.org> wrote:
> On Wed, May 12, 2021, at 4:40 PM, Alexander Kanavin wrote:
> > For ostree, yes:
> > http://git.openembedded.org/meta-openembedded/log/?h=master-next
> >
> > For the generic case, no. It's not a good idea to start guessing what
> > the upstream did.
>
> What is the goal of the `branch=` specification? I can understand it
> being *informative* for humans specifically when things like
> non-master/main branches e.g. `release-4.x`, `lts-`, `stable-` etc. are
> involved.
>
> But why is bitbake explicitly checking it? Is it to validate what the
> human expressed, or is it to try to cover some security aspect? Something
> else?
>
To ensure the specified revision is actually linked with the specified
branch, and not just free-floating, and catch branch renames, deletions and
force pushes. You can override that behaviour with nobranch=1, at your own
risk - free-floating revisions can be 'garbage collected'.
Yes, it's annoying when the upstream renames branches, but it's no
different than upstreams clearing up old tarballs, or disappearing
altogether. Ensure you have proper download mirrors.
Alex
[-- Attachment #2: Type: text/html, Size: 1711 bytes --]
next prev parent reply other threads:[~2021-05-12 21:17 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 [this message]
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
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='CANNYZj-PSq4bAQpy3s=8Vuqk-PcstZZFPzr710VXfS3Lj8Aiow@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=walters@verbum.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.