All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] How to handle external kernel patches in oe the	right way?
Date: Wed, 5 Sep 2007 22:14:37 +0100	[thread overview]
Message-ID: <20070905211437.GA10460@cimmeria> (raw)
In-Reply-To: <1189021941.7849.46.camel@localhost.localdomain>

On Wed, Sep 05, 2007 at 08:52:21PM +0100, Richard Purdie wrote:
> 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.
> 
Maybe if I get some free time around october I might suggest enhancing
the fetcher/patcher so that any URL can have a

http://blah.com/patches.gz;patchseries=1
svn://wibble.com/branchs/smoo/;patchseries=1

And it does the right thing.

Or am I going backwards?

Graeme




  reply	other threads:[~2007-09-05 21:17 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
2007-09-05 21:14         ` Graeme Gregory [this message]
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=20070905211437.GA10460@cimmeria \
    --to=dp@xora.org.uk \
    --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.