rev 5044 - www/v2/pages
Ana Beatriz Guerrero López
ana at alioth.debian.org
Sun Dec 3 17:20:00 CET 2006
Author: ana
Date: 2006-12-03 17:20:00 +0100 (Sun, 03 Dec 2006)
New Revision: 5044
Modified:
www/v2/pages/kde-bugzilla-survival-guide
Log:
Fixing some format
Modified: www/v2/pages/kde-bugzilla-survival-guide
===================================================================
--- www/v2/pages/kde-bugzilla-survival-guide 2006-12-03 16:05:03 UTC (rev 5043)
+++ www/v2/pages/kde-bugzilla-survival-guide 2006-12-03 16:20:00 UTC (rev 5044)
@@ -1,18 +1,21 @@
<h2>Survival guide to the kde bugzilla</h2>
-<p>
-Many of the kde packages fear the kde bugzilla, mostly because it is quite easy to get lost and really hard to find the right bugs in the right packages. Very often, you are met by the phrase <em>zarro boogs found</em> or alternatively you get too many bug reports.</p>
-<p>
-Starting the search from the right pages might help a bit, but very often, creating hand-crafted urls actually is the fastest. In the following parts, it will be described where to start and a couple of hand crafted urls will also be shown</p>
+<p>Many of the kde packages fear the kde bugzilla, mostly because it is quite easy to get lost and really hard to find the right bugs in the right packages. Very often, you are met by the phrase <em>zarro boogs found</em> or alternatively you get too many bug reports.</p>
+
+<p>Starting the search from the right pages might help a bit, but very often, creating hand-crafted urls actually is the fastest. In the following parts, it will be described where to start and a couple of hand crafted urls will also be shown</p>
+
<h3>Starting in kde bugzilla</h3>
-The offical entrance is at <a href="http://bugs.kde.org">http://bugs.kde.org</a> and here is a lot of links to different places. The most useful search page is the <a href="http://bugs.kde.org/query.cgi">Query reports (complex)</a> page. It gives a lot of possibilities to make different searches.<br />
-On newly reported rc bugs, the two pages with the newly reported bugs in kde might also be of some kind of help. This is the bugs opened today and the bugs opened within the last 3 days. Doing deep linking to those is not easy, as the links are dynamically generated.<br />
+<p>The offical entrance is at <a href="http://bugs.kde.org">http://bugs.kde.org</a> and here is a lot of links to different places. The most useful search page is the <a href="http://bugs.kde.org/query.cgi">Query reports (complex)</a> page. It gives a lot of possibilities to make different searches.</p>
+<p>On newly reported rc bugs, the two pages with the newly reported bugs in kde might also be of some kind of help. This is the bugs opened today and the bugs opened within the last 3 days. Doing deep linking to those is not easy, as the links are dynamically generated.</p>
+
<h3>Handcrafting urls</h3>
+<p> By looking on the url generated by the <a href="http://bugs.kde.org/query.cgi">Query reports (complex)</a> page, it is often both faster and easier to just change the url instead of creating a entire new search.</p>
+
+<p>For example, this url http://bugs.kde.org/buglist.cgi?product=<strong>kcontrol</strong>&component=<strong>kcmaccessibility</strong>&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED &bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED shows all open bugs and all resolved bugs in the kcmaccessibility module of kcontrol. To only show the open bugs, just remove the &bug_status=RESOLVED&bug_status=CLOSED from the url.</p>
+
+<p>And the following url shows all bugs in kgpg product: http://bugs.kde.org/buglist.cgi?product=<strong>kgpg</strong>&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED &bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED</p>
+
+<p>Searching can also often be interesting. The following url is good to use for searching:
+http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=<strong>UTF8</strong> &long_desc_type=allwordssubstr&long_desc=&product=<strong>konsole</strong>&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED &bug_status=CLOSED&order=Reuse+same+sort+as+last+time&cmdtype=doit which is all bugs about the string "utf8" in konsole </p>
<p>
-By looking on the url generated by the <a href="http://bugs.kde.org/query.cgi">Query reports (complex)</a> page, it is often both faster and easier to just change the url instead of creating a entire new search.<br />
-For example, this url http://bugs.kde.org/buglist.cgi?product=<strong>kcontrol</strong>&component=<strong>kcmaccessibility</strong>&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED shows all open bugs and all resolved bugs in the kcmaccessibility module of kcontrol. To only show the open bugs, just remove the &bug_status=RESOLVED&bug_status=CLOSED from the url.<br />
-And the following url shows all bugs in kgpg product: http://bugs.kde.org/buglist.cgi?product=<strong>kgpg</strong>&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED<br />
-Searching can also often be interesting. The following url is good to use for searching: http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=<strong>UTF8</strong>&long_desc_type=allwordssubstr&long_desc=&product=<strong>konsole</strong>&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED&order=Reuse+same+sort+as+last+time&cmdtype=doit which is all bugs about the string "utf8" in konsole
-</p>
-<p>
The easiest thing is often to create a appropriate query that gives 100-200 results and quick read thru the bug titles.
</p>
More information about the pkg-kde-commits
mailing list