From 624ab6d711dee76e6f80326f408047a1684a7714 Mon Sep 17 00:00:00 2001 From: Mark Linimon Date: Thu, 20 Oct 2005 06:28:37 +0000 Subject: [PATCH] Move two sentences a little bit later in 'when to submit' and slightly modify the first one. This is part of a larger set of changes that are coming. --- .../articles/problem-reports/article.sgml | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/en_US.ISO8859-1/articles/problem-reports/article.sgml b/en_US.ISO8859-1/articles/problem-reports/article.sgml index 3b6b7156b0..c8e9156d84 100644 --- a/en_US.ISO8859-1/articles/problem-reports/article.sgml +++ b/en_US.ISO8859-1/articles/problem-reports/article.sgml @@ -127,14 +127,7 @@ - Another thing is that if the system on which you experienced - the bug is not fairly up-to-date, you should seriously consider - upgrading and trying to reproduce the problem on an up-to-date - system before submitting a problem report. There are few things - that will annoy a developer more than receiving a problem report - about a bug she has already fixed. - - Finally, a bug that can not be reproduced can rarely be + A bug that can not be reproduced can rarely be fixed. If the bug only occurred once and you can not reproduce it, and it does not seem to happen to anybody else, chances are none of the developers will be able to reproduce it or figure @@ -144,6 +137,11 @@ these kinds of bugs are actually caused by failing hard drives or overheating processors — you should always try to rule out these causes, whenever possible, before submitting a PR. + + Then you should ascertain whether or not the problem is + timely. There are few things + that will annoy a developer more than receiving a problem report + about a bug she has already fixed.