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 20:52:21 +0100 [thread overview]
Message-ID: <1189021941.7849.46.camel@localhost.localdomain> (raw)
In-Reply-To: <1434447296.20070905205215@vanille-media.de>
On Wed, 2007-09-05 at 20:52 +0200, Dr. Michael Lauer wrote:
> Koen Kooi wrote:
> > Richard Purdie schreef:
> > I'm having issues with crap like do_prepatch. Patches are only
> applied by patch.bbclass,
> > not some hand written voodoo <period>.
>
> Very well. If it annoys you so much, feel free to enhance patch.bbclass to
> deal with upstream series files while retaining OE-added patches to it.
>
> Until then, I think we shouldn't make life more complicated for the
> actual upstream developers just because of going a bit too far wrt. to
> our principles.
I'm afraid I'm with Mickey here. I don't like the way this "prepatching"
works and I think its pretty ugly but I can understand why people are
doing it. I'd like to see a better solution but until then what they're
doing allows them to develop effectively which is what we're supposed to
be about.
Cheers,
Richard
next prev parent reply other threads:[~2007-09-05 19:55 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
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 [this message]
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=1189021941.7849.46.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