Over on cygwin-xfree@ we find XWin's logs to be important information in
diagnosing problems. I would like to make this standard procedure for
issue reporting just like cygcheck output is currently.
Patch for bugs.html attached.
Yaakov
Cygwin/X
Index: bugs.html
===================================================================
RCS file: /cvs/cygwin/htdocs/bugs.html,v
retrieving revision 1.121
diff -u -r1.121 bugs.html
--- bugs.html 26 Sep 2007 09:42:02 -0000 1.121
+++ bugs.html 28 Oct 2009 02:05:38 -0000
@@ -121,6 +121,12 @@
otherwise encode the output. Just attach it as a straight text file so
that it can be easily viewed.</li></b><br>
+<a name="xwin-log">
+<li>Similarly, if your problem involves Cygwin/X, include the file
+<tt>/var/log/XWin.0.log</tt> in addition to your cygcheck output as
+<em>plain-text attachments</em> in your report. Please note that
+Cygwin/X has its own <a href="lists.html">mailing list</a>.</li><br>
+
<a name="the-problem">
<li>Do not assume that your problem is so trivial or so
"well known" that it does not require any details or background from