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

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

+ Antoine Pitrou + solipsis at pitrou.net +
+ Wed Jan 11 20:19:46 CET 2012 +

+
+ +
On Wed, 11 Jan 2012 13:33:41 -0500
+Juan Luis Baptiste <juancho at mageia.org>
+wrote:
+> On Wed, Jan 11, 2012 at 1:22 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
+> > On Wed, 11 Jan 2012 12:43:35 -0500
+> > But how do you choose which patches you want to backport from the
+> > stream of bugfixes done by upstream?
+> 
+> Because normally a single commit fixes a single bug and the commit
+> message says it clearly, so it's easy to spot the fixes.
+> 
+> > Should the packager monitor all
+> > bug fixing activity? (sure (s)he *can*, but that's a lot of work)
+> >
+> 
+> No we don't need to, we just need to look for the fix we are
+> interested in as I described before.
+
+Uh, you have a hard time understanding a question don't you?
+
+I specifically asked *how* you come to be interested in a particular
+fix, rather than all of them.
+
+So, again, do you monitor all commits or is there another heuristic you
+apply to avoid that O(n) process?
+
+Regards
+
+Antoine.
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

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