From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110408/003907.html | 72 +++++++++++++++++++++++++++++++++ 1 file changed, 72 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110408/003907.html (limited to 'zarb-ml/mageia-dev/20110408/003907.html') diff --git a/zarb-ml/mageia-dev/20110408/003907.html b/zarb-ml/mageia-dev/20110408/003907.html new file mode 100644 index 000000000..cc491a30f --- /dev/null +++ b/zarb-ml/mageia-dev/20110408/003907.html @@ -0,0 +1,72 @@ + + + + [Mageia-dev] Bugzilla + + + + + + + + + +

[Mageia-dev] Bugzilla

+ Ahmad Samir + ahmadsamir3891 at gmail.com +
+ Fri Apr 8 15:31:29 CEST 2011 +

+
+ +
On 8 April 2011 10:06, James Kerr <jim at jkerr82508.free-online.co.uk> wrote:
+> When marking a bug as a duplicate, bugzilla insists that a comment be added.
+> This seems redundant since bugzilla itself adds an explanatory comment
+> automatically.
+>
+> Is it possible to make an exception in this case, to the requirement to add
+> a comment when changing the status of a bug?
+>
+> Jim
+>
+
+That's a side effect of a change in bugzilla that aims to make it
+mandatory to add a comment when closing a bug as fixed... but ideally
+not when marking as a duplicate.
+
+-- 
+Ahmad Samir
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1