From: Otto Wyss <otto.wyss@orpatec.ch>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Where is a current fbdev tree
Date: Wed, 06 Oct 2004 22:45:59 +0200 [thread overview]
Message-ID: <41645988.104D80DD@orpatec.ch> (raw)
In-Reply-To: 200410070351.23449.adaplas@hotpop.com
"Antonino A. Daplas" wrote:
>
> On Thursday 07 October 2004 01:34, Alexander Kern wrote:
> > Hello, I search for current location of fbdev tree. Preferably diff patch
> > against vanilla or mm tree.
> >
>
> Consider Andrew's mm tree as containing the latest fbdev changes.
>
I would be much better to have the latest fbdev changes here on this
site and use kbuild. So any kernel sources could be used.
O. Wyss
--
See a huge pile of work at "http://wyodesktop.sourceforge.net/"
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-06 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 17:34 Where is a current fbdev tree Alexander Kern
2004-10-06 19:51 ` Antonino A. Daplas
2004-10-06 20:45 ` Otto Wyss [this message]
2004-10-08 21:35 ` Antonino A. Daplas
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=41645988.104D80DD@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).