On 04/03/2013 01:44 PM, Nick Podolak wrote:
On Wed, Apr 3, 2013 at 12:36 PM, Jonathan Bither <jonbit...@gmail.com
<mailto:jonbit...@gmail.com>> wrote:

    May be the completely wrong idea, but what if there was an
    OpenWRT-Kernel GIT repository holding the branches and modifications
    required for each arch. Would allow easy updates and backports from
    a Trunk branch to an LTS one.


    On 04/03/2013 12:31 PM, Bruno Wolff III wrote:

        On Wed, Apr 03, 2013 at 18:16:05 +0200,
            Rafał Miłecki <zaj...@gmail.com <mailto:zaj...@gmail.com>>
        wrote:


            Ohh, so there is policy of *not* doing *fixes* updates of
            the kernel?
            So we don't update for example from 3.4.30 to 3.4.38 after
            branching?

            If so, I had no idea about that, but it sounds pretty wrong.
            Minor
            (fixes) updates usually contain regression and security fixes.


        I wouldn't say policy as much as observed behavior.
        _________________________________________________
        openwrt-devel mailing list
        openwrt-devel@lists.openwrt.__org
        <mailto:openwrt-devel@lists.openwrt.org>
        https://lists.openwrt.org/__mailman/listinfo/openwrt-devel
        <https://lists.openwrt.org/mailman/listinfo/openwrt-devel>

    _________________________________________________
    openwrt-devel mailing list
    openwrt-devel@lists.openwrt.__org
    <mailto:openwrt-devel@lists.openwrt.org>
    https://lists.openwrt.org/__mailman/listinfo/openwrt-devel
    <https://lists.openwrt.org/mailman/listinfo/openwrt-devel>


Jon,

That basically exists today already in the buildroot system.  It's just
not a plain git repo.  The patches folders in target/generic and then
for each target/<arch> are numerous but relatively organized.
Oh I know. I just meant that it may be easier to manage. and cherry-pick

Rafa, Imre, Bruno,

I'm not convinced that it makes sense to target an LTS kernel every
release either, but I firmly believe that an LTS kernel should be
targeted at least once every 2 years or so.  A policy like this makes it
easier to pull upstream *fixes*, in theory, for both maintainers and
tinkerers even if that isn't the current modus operandi.




_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to