From: Trevor Woerner <twoerner@gmail.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: yocto@yoctoproject.org, 'Gary Thomas' <gary@mlbassoc.com>
Subject: Re: ***SPAM*** Re: [meta-raspberrypi] Current master broken
Date: Tue, 6 Dec 2016 21:17:55 -0500 [thread overview]
Message-ID: <20161207021755.GA9669@openSUSE-i7.site> (raw)
In-Reply-To: <20161206230034.3f25f7b2@nuc.betafive.co.uk>
On Tue 2016-12-06 @ 11:00:34 PM, Paul Barker wrote:
> Upstream effectively support one version, currently 4.4. When upstream
> made that the default branch, the changes to the 4.1 branch stopped -
> there wasn't really much overlap. Everything post-4.4 is active
> development and gets rebased at will. At some point they'll move to the
> next LTS release (4.9) and 4.4 will be dropped.
Are you speaking specifically about the kernel for raspberry pi, or in
general? Because the kernel for raspberry pi has several branches that are all
maintained and kept up-to-date. It's actually quite commendable how this
repository is maintained. Branches for 4.4, 4.7, 4.8, 4.9 and others are all
usable (ignoring the constant rebasing thing...)
> I'd class all recipes for kernel versions other than default branch
> upstream as experimental. Perhaps we should just go with AUTOREV here?
> Anything else is going to need changing really often.
Not every revision of those branches are usable for raspberry pi. Someone
named "popcornmix" has been keeping everything aligned with upstream, and
merging in the support for raspberry pi.
If you took the rpi-4.8.y branch, for example, and happened to check out
commit 356ccf6d2b0cfe9dca6c5d961bfd04dc8c0f4e64, you wouldn't have something
that would build.
The problem is they keep rebasing, which messes up the SRC_URIs :-(
next prev parent reply other threads:[~2016-12-07 2:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 7:33 [meta-raspberrypi] Current master broken Gary Thomas
2016-12-03 14:16 ` Paul Barker
2016-12-05 0:54 ` Andrei Gherzan
2016-12-05 6:03 ` Gary Thomas
2016-12-05 16:50 ` Khem Raj
2016-12-06 15:29 ` Andrei Gherzan
2016-12-06 18:04 ` ***SPAM*** " Herve Jourdain
2016-12-06 18:11 ` Andrei Gherzan
2016-12-06 21:21 ` Herve Jourdain
2016-12-06 23:00 ` Paul Barker
2016-12-07 2:17 ` Trevor Woerner [this message]
2016-12-07 7:25 ` Paul Barker
2016-12-07 7:42 ` Paul Barker
2016-12-07 10:54 ` Andreas Müller
2016-12-06 22:50 ` Paul Barker
2016-12-07 15:19 ` Andrea Galbusera
2016-12-07 15:23 ` Andrei Gherzan
2016-12-03 20:18 ` Herve Jourdain
2016-12-06 21:32 ` Trevor Woerner
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=20161207021755.GA9669@openSUSE-i7.site \
--to=twoerner@gmail.com \
--cc=gary@mlbassoc.com \
--cc=paul@paulbarker.me.uk \
--cc=yocto@yoctoproject.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.