Date: Thu, 20 Nov 2008 17:48:43 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Robert Noland <rnoland@freebsd.org> Cc: "Carlos A. M. dos Santos" <unixmania@gmail.com>, Gabor Pali <pgj@freebsd.org>, ports-committers@freebsd.org, cvs-all@freebsd.org, cvs-ports@freebsd.org Subject: Re: cvs commit: ports MOVED Message-ID: <20081120064843.GV51761@server.vk2pj.dyndns.org> In-Reply-To: <1227051188.1636.4.camel@wombat.2hip.net> References: <200811181410.mAIEAHkK051871@repoman.freebsd.org> <e71790db0811180651sd5fb6cfg9a604f376ad7aee6@mail.gmail.com> <1227051188.1636.4.camel@wombat.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--37nyS7qXrnu4wN2o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Nov-18 18:33:08 -0500, Robert Noland <rnoland@freebsd.org> wrote: >I do agree with flz. All of the xorg provided drivers follow the >xf86-xxx-xxx naming convention. I'll take the opposing PoV and suggest that xf86-input-xxx can be interpreted as 'X.org driver supporting input from device xxx' whereas 'input-xxx' doesn't indicate what it interfaces to. > I don't really care what it is called, >as long as one can clearly determine what drivers are provided by xorg >and which are not. Why is this important? --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --37nyS7qXrnu4wN2o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkklCEsACgkQ/opHv/APuIfb6wCglSKNbia+cUGkUnD9YQcS1Vxw xUAAoJn/gBRIO7BpSWf5eyKVmedf6gwF =JAah -----END PGP SIGNATURE----- --37nyS7qXrnu4wN2o--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081120064843.GV51761>