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/010219.html | 102 +++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010219.html (limited to 'zarb-ml/mageia-dev/2011-December/010219.html') diff --git a/zarb-ml/mageia-dev/2011-December/010219.html b/zarb-ml/mageia-dev/2011-December/010219.html new file mode 100644 index 000000000..83bfa7ce3 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010219.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] RFC: Opening Backports (once again...) + + + + + + + + + +

[Mageia-dev] RFC: Opening Backports (once again...)

+ Maarten Vanraes + alien at rmail.be +
+ Tue Dec 6 08:28:45 CET 2011 +

+
+ +
Op dinsdag 06 december 2011 00:29:03 schreef Anssi Hannula:
+> On 06.12.2011 00:56, Thomas Backlund wrote:
+> > Now,
+> > 
+> > here comes the question about backports once again.
+[...]
+> > Using a separate branch is also a cleaner way of providing
+> > backports, and makes it easy to separate changes needed only
+> > for Cauldron (or backports).
+> 
+> Hm, how does this help with enabling backports (i.e. compared to simply
+> using cauldron repo)?
+
+not sure, but i thought the problem we're facing now was that submitting from 
+cauldron to backports was a "problem" in security scripting, ie: not being 
+able to specify 2 sources? than this would solve that problem?
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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