From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: SRCREV defined too late -how to fix?
Date: Thu, 8 Apr 2010 08:14:13 +0200 [thread overview]
Message-ID: <20100408061413.GC3269@jama> (raw)
In-Reply-To: <20100408060727.GB3269@jama>
On Thu, Apr 08, 2010 at 08:07:27AM +0200, Martin Jansa wrote:
> To be honest SRCREV in linux-ixp4xx.inc is really strange, I put it
> there as it's as close to previous state as possible (same SRCREV is
> share between all versions of linux-ixp4xx recipe). I would expect
> different SRCREV of patchset for different module=${KERNEL_RELEASE} (I
> think it's harder to test all KERNEL_RELEASEs when you need to bump
> patchset SRCREV for latest RELEASE or unnecesarry kernel upgrades for
> users of older KERNEL_RELEASE when someone bumped patches only to get
> more patches for latest RELEASE without any change in their old version.
To finish my thought..
With this new layout (SRCREV in recipe) it will be much easier to bump
SRCREV ie only for linux-ixp4xx_2.6.29.bb (overwritting shared SRCREV
from linux-ixp4xx.inc after its include), but be aware that if you put
SRCREV_pn-linux-ixp4xx in distro config you will also overwrite this
locally bumped SRCREV which can be confusing a bit.
Regards,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
prev parent reply other threads:[~2010-04-08 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 13:50 SRCREV defined too late -how to fix? Mike Westerhof
2010-04-06 15:26 ` Chris Larson
2010-04-08 3:07 ` Mike Westerhof
2010-04-08 4:18 ` Martin Jansa
2010-04-08 5:19 ` Mike Westerhof
2010-04-08 6:07 ` Martin Jansa
2010-04-08 6:14 ` Martin Jansa [this message]
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=20100408061413.GC3269@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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.