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/2013-January/021338.html | 91 +++++++++++++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-January/021338.html (limited to 'zarb-ml/mageia-dev/2013-January/021338.html') diff --git a/zarb-ml/mageia-dev/2013-January/021338.html b/zarb-ml/mageia-dev/2013-January/021338.html new file mode 100644 index 000000000..2997732b1 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/021338.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] RPM group change before Beta 2 + + + + + + + + + +

[Mageia-dev] RPM group change before Beta 2

+ AL13N + alien at rmail.be +
+ Tue Jan 8 20:48:36 CET 2013 +

+
+ +
Op zondag 6 januari 2013 23:24:34 schreef Pierre-Malo Deniélou:
+> Le 06/01/13 23:22,Joseph Wang nous adresse ces quelques mots :
+> > Sure thing.  I can start patching some of the rpms that aren't haven't
+> > been done yet.  However, I was wondering if I can do that with just
+> > subversion commit privileges or do I need to be able to submit build
+> > requests to do this?
+> 
+> To patch, you do not need to submit. But it's good practice to contact
+> the maintainer when you do that: IRC is a fast way to do that.
+> 
+> Cheers,
+
+in particular, on #mageia-dev the Sophie bot can tell you which maintainer is 
+from which package by:
+
+:maint <package>
+
+also, if it tells nobody, you can still see who last Packaged it
+
+with "mgarepo log <package>"
+
+or on irc with ":p -s <package>"
+
+ + + + + + + + + + + + + + + + +
+

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