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/2011-December/010847.html | 73 ++++++++++++++++++++++++++++ 1 file changed, 73 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010847.html (limited to 'zarb-ml/mageia-dev/2011-December/010847.html') diff --git a/zarb-ml/mageia-dev/2011-December/010847.html b/zarb-ml/mageia-dev/2011-December/010847.html new file mode 100644 index 000000000..20cdfa6d5 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010847.html @@ -0,0 +1,73 @@ + + + + [Mageia-dev] [changelog] [RPM] 1 core/updates_testing firefox-9.0-0.1.mga1 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] 1 core/updates_testing firefox-9.0-0.1.mga1

+ Sander Lepik + sander.lepik at eesti.ee +
+ Sat Dec 31 17:57:21 CET 2011 +

+
+ +
31.12.2011 18:40, Thierry Vignaud kirjutas:
+>> I'am not trolling. I know that you maintain some firefox-ext in cauldron
+>> and that you are away sometime.
+>> I only said that since some months, nobody was checking the extensions
+>> in mga *1*.
+>> (and iirc QA don't check it anymore, as you can see in the updates of
+>> firefox 6 or later)
+> Then, as firefox tries itself to update extensions to their latest version,
+> I see no reason to add an exception for firefox extensions and just
+> update them to their latest version from cauldron when pushing a
+> firefox update.
+That should be done by the extension maintainer. If maintainer wants to keep them in Mageia 
+(s)he should also keep them up-to-date.
+
+--
+Sander
+
+
+ + + +
+

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