From: Michel Dänzer <daenzerm@student.ethz.ch>
To: Adam Lebsack <lebsack@mac.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: XF86Config 4.0
Date: Mon, 26 Jun 2000 11:15:44 +0200 [thread overview]
Message-ID: <39571F40.5D42D578@student.ethz.ch> (raw)
In-Reply-To: a04320401b57cb5cfa010@[192.168.0.3]
Adam Lebsack wrote:
>
> At 9:16 PM +0200 6/22/00, Michel Dänzer wrote:
> >Adam Lebsack wrote:
> >>
> >> What is the status on xf86config for 4.0? Is anybody working on
> >> this? It would be nice to be on par with the x86 world when
> >> configuring X.
> >
> >There is a new tool in the works, it's called xf86cfg, it's written in perl
> >and should be working in 4.0.1 which should be out in a few weeks' time.
> >
> >It will be graphical and should work on all platforms :)
> >
>
> How can I become involved in its development? Is it in CVS?
Yep, in the XFree86 CVS, so you'd currently have to join as a developer.
If you don't want to do that, you'll have to wait for either
- the 4.0.1 release
- public anonymous CVS access
both of which should be available RSN.
Michel
--
It is easier to fix Unix than to live with NT.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-26 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-22 19:11 XF86Config 4.0 Adam Lebsack
2000-06-22 19:16 ` Michel Dänzer
2000-06-26 7:25 ` Adam Lebsack
2000-06-26 7:43 ` Miles Lane
2000-06-26 9:15 ` Michel Dänzer [this message]
2000-06-26 10:11 ` Geert Uytterhoeven
2000-06-26 10:31 ` Michel Dänzer
2000-06-26 19:17 ` Adam Lebsack
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=39571F40.5D42D578@student.ethz.ch \
--to=daenzerm@student.ethz.ch \
--cc=lebsack@mac.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).