[Mplayer-cvslog] CVS: main/DOCS bugreports.html,1.28,1.29
Diego Biurrun CVS
diego at mplayerhq.hu
Thu Jun 20 13:52:54 CEST 2002
Update of /cvsroot/mplayer/main/DOCS
In directory mail:/var/tmp.root/cvs-serv4201/DOCS
Modified Files:
bugreports.html
Log Message:
HTML mail not wanted, mplayer --> <B>MPlayer</B>.
Index: bugreports.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/bugreports.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- bugreports.html 16 Jun 2002 11:24:49 -0000 1.28
+++ bugreports.html 20 Jun 2002 11:52:51 -0000 1.29
@@ -13,8 +13,8 @@
<P><B>How to report bugs?</B></P>
-<P>First of all please try the latest CVS version of mplayer as your bug might
-already be fixed there. CVS instructions can be found at the bottom of
+<P>First of all please try the latest CVS version of <B>MPlayer</B> as your bug
+might already be fixed there. CVS instructions can be found at the bottom of
<A HREF="http://www.mplayerhq.hu/homepage/dload.html">this page</A>.</P>
<P>If this did not help please refer to <A HREF="documentation.html#D">Appendix D</A>
@@ -24,7 +24,7 @@
<P>If you feel have the necessary skills you are invited to have a go at fixing
the bug yourself. Or maybe you already did that? Please read
<A HREF="tech/patches.txt">this short document</A> to find out how to get your
-code included in mplayer. The people on the
+code included in <B>MPlayer</B>. The people on the
<A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A>
mailing list can assist you if you have questions.</P>
@@ -33,16 +33,19 @@
<P>Subscribe to the mplayer-users mailing list:<BR>
<A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR>
and send your bug report to:<BR>
- <A HREF="mailto:mplayer-users at mplayerhq.hu">mplayer-users at mplayerhq.hu</A><BR>
-Please note that we will not individually CC (carbon-copy) people so it is a good
-idea to subscribe to actually receive your answer.</P>
+ <A HREF="mailto:mplayer-users at mplayerhq.hu">mplayer-users at mplayerhq.hu</A></P>
+
+<P>The language of this list is <B>English</B>. Please follow the standard
+<A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and
+<B>do not send HTML mail</B> to to any of our mailing lists. You will only get
+ignored or banned. Also note that we will not individually CC (carbon-copy)
+people so it is a good idea to subscribe to actually receive your answer.</P>
<P>Please do not send bug reports privately to individual developers. This is
community work and thus there might be several people interested in it.
Also sometimes other users already experienced your troubles and have a
-solution in hand how to circumvent a problem even if it is a bug in mplayer
-code.<BR>
-The language of this list is <strong>English</strong>.</P>
+solution in hand how to circumvent a problem even if it is a bug in <B>MPlayer</B>
+code.</P>
<P>Please describe your problem as detailed as possible with examples etc.
and do not forget to include this valuable information:</P>
@@ -125,10 +128,10 @@
<P><B>For playback problems</B></P>
-<P>Please include the output of mplayer at verbosity level 1, but remember to
-<B>not truncate the output</B> when you paste it into your mail. The developers need
-all of the messages to properly diagnose a problem. You can direct the output
-into a file like this:</P>
+<P>Please include the output of <B>MPlayer</B> at verbosity level 1, but
+remember to <B>not truncate the output</B> when you paste it into your mail. The
+developers need all of the messages to properly diagnose a problem. You can
+direct the output into a file like this:</P>
<P><CODE> mplayer -v [options] [filename] &> mplayer.log</CODE></P>
@@ -140,7 +143,7 @@
<P>Also upload a small text file having the same base name as your file
with a .txt extension. Describe the problem you are having with the
particular file there and include your email address as well as the output
-of mplayer at verbosity level 1.<BR>
+of <B>MPlayer</B> at verbosity level 1.<BR>
Usually the first 1-5 MB of a file are enough to reproduce the problem,
but to be sure we ask you to:
<P><CODE> dd if=yourfile of=smallfile bs=1024k count=5</CODE></P>
@@ -156,7 +159,8 @@
<P><B>For crashes</B></P>
-<P>If you have a core dump of the crash continue reading the next paragraph, otherwise skip it.</P>
+<P>If you have a core dump of the crash continue reading the next paragraph,
+otherwise skip it.</P>
<P><B>How to extract meaningful information from a core dump</B></P>
@@ -177,10 +181,10 @@
<P> <CODE>gdb mplayer --core=core -batch --command=command_file > mplayer.bug</CODE></P>
<P><B>How to conserve information about a reproducible crash</B></P>
-<P>Re-compile mplayer with debugging code enabled:</P>
+<P>Recompile <B>MPlayer</B> with debugging code enabled:</P>
<P><CODE> ./configure --enable-debug=3<BR>
make</CODE></P>
-and then run mplayer within gdb using:
+and then run <B>MPlayer</B> within gdb using:
<P><CODE> gdb mplayer</CODE></P>
<P>You are now within gdb. Type:</P>
@@ -200,7 +204,7 @@
<P><B>I know what I am doing...</B></P>
<P>If you created a proper bug report following the steps above and you are
-confident it is a bug in mplayer, not a compiler problem or broken file,
+confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken file,
you have already read the documentation and you could not find a solution,
your sound drivers are OK, then you might want to subscribe to the
mplayer-advusers list and send your bug report there to get a better and
@@ -209,7 +213,7 @@
in the manual there, you will be ignored or flamed instead of getting an
appropriate answer.<BR>
So do not flame us and subscribe to -advusers only if you really know
-what you are doing and feel like being an advanced mplayer user or
+what you are doing and feel like being an advanced <B>MPlayer</B> user or
developer. If you meet these criteria it should not be difficult to find
out how to subscribe...
</P>
More information about the MPlayer-cvslog
mailing list