From: Otto Wyss <otto.wyss@orpatec.ch>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: kbuild
Date: Sun, 26 Sep 2004 08:52:36 +0200 [thread overview]
Message-ID: <41566735.4C930648@orpatec.ch> (raw)
In-Reply-To: 20040924170315.GA11905@dreamland.darkstar.lan
Kronos wrote:
>
> It's very simple, a skeleton would be like that:
>
It would be terrible nice if someone could work out a goood sample, test
it out and send it to me. IMO it's important for the success of
linux-fbdev but I simply don't have the time to do it myself.
O. Wyss
--
See a huge pile of work at "http://wyodesktop.sourceforge.net/"
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
prev parent reply other threads:[~2004-09-26 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 16:48 kbuild Otto Wyss
2004-09-24 17:03 ` kbuild Kronos
2004-09-26 6:52 ` Otto Wyss [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=41566735.4C930648@orpatec.ch \
--to=otto.wyss@orpatec.ch \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).