From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] How to handle external kernel patches in oe the right way?
Date: Wed, 05 Sep 2007 17:58:06 +0100 [thread overview]
Message-ID: <1189011486.7849.35.camel@localhost.localdomain> (raw)
In-Reply-To: <20070904202957.GD1429@dodger.lab.datenfreihafen.org>
On Tue, 2007-09-04 at 22:29 +0200, Stefan Schmidt wrote:
> Due to my work on OpenEZX (http://www.openezx.org) I'm in touch with
> external kernel patches used in OE to build working kernels for
> different Motorola mobile phones.
>
> Talking with Koen about the best way to handle this we have some
> slightly different opinions on this. So we like to get some more
> opinions on this before pinning to a strategy.
>
> Koen like to pull the patches from a known-good rev into oe to have
> them all at one place for less fragile building and tweaking.
>
> I prefer OE to use our svn server with a fixed SRCREV which gets
> updated once a newer version is known good. I'm not a fan of
> duplicating the patches in OE if some small tweaking patches can also
> handle it.
Personally I agree with this in principle, I've never liked maintaining
kernel patches in OE directly either.
Cheers,
Richard
next prev parent reply other threads:[~2007-09-05 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 20:29 [RFC] How to handle external kernel patches in oe the right way? Stefan Schmidt
2007-09-04 22:21 ` Rod Whitby
2007-09-05 11:48 ` Nils Faerber
2007-09-05 17:36 ` Justin Patrin
2007-09-05 16:58 ` Richard Purdie [this message]
2007-09-05 17:39 ` Koen Kooi
2007-09-05 18:52 ` Dr. Michael Lauer
2007-09-05 19:49 ` Koen Kooi
2007-09-05 22:53 ` Dr. Michael Lauer
2007-09-05 19:52 ` Richard Purdie
2007-09-05 21:14 ` Graeme Gregory
2007-09-05 22:45 ` Dr. Michael Lauer
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=1189011486.7849.35.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox