<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Wed, 2011-03-16 at 03:29 -0600, Matt Dew wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">I'm all for keeping it easy for the devs to edit and review patches. I </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">have a nervous twitch in my stomach about format proliferation though. </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">I do not want to end up back where we were a year ago.</FONT></TT><BR>
</BLOCKQUOTE>
I was somewhat concerned about that, but I don't see a line-up of people proposing<BR>
new docs. On the other hand, getting any documentation to be written, in any format,<BR>
has always been a challenge for any software project. It's a risk I am willing to take.<BR>
<BR>
While on the subject, the following protos have their original txt file.<BR>
Any candidates for docbook/asciidoc conversion. I know I have been asking this<BR>
before and I was told there were "no plans" for doing it. This was before the docbook<BR>
conversion. Perhaps now would be a good time to have a plan.<BR>
<BR>
They just look silly now that every thing else is converted.<BR>
<BR>
<BLOCKQUOTE>
<PRE>
compositeproto.txt
damageproto.txt
dri2proto.txt
fixesproto.txt
randrproto.txt
renderproto.txt
xv-protocol-v2.txt
</PRE>
</BLOCKQUOTE>
<BR>
<BR>
<BR>
</BODY>
</HTML>