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/2012-January/011249.html | 100 ++++++++++++++++++++++++++++ 1 file changed, 100 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-January/011249.html (limited to 'zarb-ml/mageia-dev/2012-January/011249.html') diff --git a/zarb-ml/mageia-dev/2012-January/011249.html b/zarb-ml/mageia-dev/2012-January/011249.html new file mode 100644 index 000000000..e3e57695a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011249.html @@ -0,0 +1,100 @@ + + + + [Mageia-dev] please stop doing "bugs" for updating magia 1 + + + + + + + + + +

[Mageia-dev] please stop doing "bugs" for updating magia 1

+ Juan Luis Baptiste + juancho at mageia.org +
+ Wed Jan 11 20:43:56 CET 2012 +

+
+ +
On Wed, Jan 11, 2012 at 2:38 PM, Johnny A. Solbu <cooker at solbu.net> wrote:
+> On Wednesday 11 January 2012 19:33, Juan Luis Baptiste wrote:
+> And how do one do that without monitoring most bugfixing activity or reviewing them, hunting for a particular fix?
+>
+> To some people, that magic trick is not obvious.
+>
+
+As I said before, the upstream bug report will tell you which commit
+fixed the bug, so you go ahead and get that particular revision and
+create a patch to apply to the packages, there's no need to monitor
+*all* bugfixing activity, you just look for what you need when you
+need to.
+
+-- 
+Juancho
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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