From: Kevin_Hendricks <khendricks@admin.ivey.uwo.ca>
To: luther@dpt-info.u-strasbg.fr
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: SuSE Rage 128 Xserver Source and XFree 3.3.6
Date: Thu, 21 Oct 1999 07:32:26 -0400 (EDT) [thread overview]
Message-ID: <199910211134.GAA16627@lists.linuxppc.org> (raw)
Hi,
>So is the Rqge 128 driver stuff already in 3.9.16 ?
>
According to the list of Xservers given on the XFree86 org page, it is NOT
included. They have completely restructured Xservers for that release. Now
they all start with the base Xserver while calls up various shared-libraries to
handle driver specifics / acceleration, etc.
Given XFree86 policy of not releasing source, (according to their website they
specifically request that people *not* join just to get access to pre-release
source). I hope SuSE simply just posts the source.
This whole process simply makes no sense. Why give development source only to a
body that can not release it for others? Not exactly using the strength of the
free software movement?
I guess I shouldn't complain, Sun won't let me release the JDK source to others
(just diffs).
Kevin
--
Kevin B. Hendricks
Associate Professor of Operations and Information Technology
Richard Ivey School of Business, University of Western Ontario
London, Ontario N6A-3K7 CANADA
khendricks@ivey.uwo.ca, (519) 661-3874, fax: 519-661-3959
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-10-21 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-21 11:32 Kevin_Hendricks [this message]
1999-10-22 16:04 ` SuSE Rage 128 Xserver Source and XFree 3.3.6 Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
1999-10-20 19:43 Kevin B. Hendricks
1999-10-20 20:05 ` anthony tong
1999-10-20 23:23 ` Kevin B. Hendricks
1999-10-20 23:25 ` Dan Burcaw
1999-10-21 0:04 ` anthony tong
1999-10-21 9:33 ` Charlie McLachlan
1999-10-21 10:44 ` Sven LUTHER
1999-10-21 19:42 ` anthony tong
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=199910211134.GAA16627@lists.linuxppc.org \
--to=khendricks@admin.ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=luther@dpt-info.u-strasbg.fr \
/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).