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/010846.html | 74 ++++++++++++++++++++++++++++ 1 file changed, 74 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010846.html (limited to 'zarb-ml/mageia-dev/2011-December/010846.html') diff --git a/zarb-ml/mageia-dev/2011-December/010846.html b/zarb-ml/mageia-dev/2011-December/010846.html new file mode 100644 index 000000000..b015212ec --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010846.html @@ -0,0 +1,74 @@ + + + + [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

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Sat Dec 31 17:40:11 CET 2011 +

+
+ +
On 29 December 2011 18:20, Manuel Hiebel <manuel at hiebel.eu> wrote:
+>> Please stop trolling.
+>> I maintain this package.
+>> I cannot access mga's BS for a week so I'm asking for someone else to
+>> push/backport the cauldron version into updates_testing along firefox-9
+>
+> 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.
+
+ + + + +
+

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