Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Henning Heinold <openembedded-devel@lists.openembedded.org>
Subject: Re: Conflicting qte patches for Simpad
Date: Thu, 12 Jul 2007 18:00:37 +0300	[thread overview]
Message-ID: <1787781246.20070712180037@gmail.com> (raw)
In-Reply-To: <20070710114840.GA16604@mi.fu-berlin.de>

Hello Henning,

Tuesday, July 10, 2007, 2:48:40 PM, you wrote:

> On Tue, Jul 10, 2007 at 11:19:46AM +0200, Henning Heinold wrote:
>> On Mon, Jul 09, 2007 at 05:24:32PM +0200, Torsten Sadowski wrote:
>> > Hi,
>> > 
>> > after some time I tried to build a Simpad opie-image again (from the devel 
>> > branch) but I encountered conflicting patches for libqte (normal, static and 
>> > mt).
>> > 
>> > It seems, that 
>> > QWSTtyKeyboardHandler::QWSTtyKeyboardHandler
>> > moved to:
>> > kernelkeyboard.cpp
>> > 
>> > which is not accounted for in the devfs.patch.
>> > 
>> > Cheers, Torsten
>> > 
>> 
>> Because linux 2.4 is unmaintained and linux 2.6 is the future devfs.patch is gone.
>> 
>> Please do mtn pull and mtn up.
>> 
>> Bye Henning

> Sorry,

> I am wrong, I thougt Mr. psokolovsky delete it with his last commit for
> qte-common_2.3.10.inc. So please delete the line
> SRC_URI_append_simpad       = "file://devfs.patch;patch=1 " alone
> and try again.

  Ok, now removed in OE too.

> Bye Henning



-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




      reply	other threads:[~2007-07-12 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 15:24 Conflicting qte patches for Simpad Torsten Sadowski
2007-07-10  9:19 ` Henning Heinold
2007-07-10 11:48   ` Henning Heinold
2007-07-12 15:00     ` Paul Sokolovsky [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=1787781246.20070712180037@gmail.com \
    --to=pmiscml@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox