From: Pavel Machek <pavel@ucw.cz>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: More Fbdev policies.
Date: Sat, 6 Jul 2002 03:14:03 +0200 [thread overview]
Message-ID: <ag7d53$ptg$2@main.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0207051302300.30731-100000@www.transvirtual.com>
Hi!
> Recently I was porting several fbdev drivers over to the new api. Some
> driver writers asked to have the changes reverted. So anyone who wants the
> drivers reverted to the previous state say so. I will revert them. I did
> this not to break any drivers but have a smooth transition. This will not
> be the case now.
>
> NOTE:
> I will begin change the upper fbdev layer monday thus breaking most
> if not all drivers. It is up to the maintainers to fix them. If not
> fixed by the end of the developement cycle they will be dropped.
End of development cycle == 2.6.0 or 2.6.20? It would probably make
sense to only mark them broken for stable series, they are pretty
likely to be fixed there.
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Got root? We do.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-06 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 20:35 More Fbdev policies James Simmons
2002-07-05 20:35 ` James Simmons
2002-07-06 1:14 ` Pavel Machek [this message]
2002-07-06 1:14 ` Pavel Machek
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='ag7d53$ptg$2@main.gmane.org' \
--to=pavel@ucw.cz \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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.