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/20110119/002260.html | 83 +++++++++++++++++++++++++++++++++ 1 file changed, 83 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110119/002260.html (limited to 'zarb-ml/mageia-dev/20110119/002260.html') diff --git a/zarb-ml/mageia-dev/20110119/002260.html b/zarb-ml/mageia-dev/20110119/002260.html new file mode 100644 index 000000000..7e1056a3c --- /dev/null +++ b/zarb-ml/mageia-dev/20110119/002260.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] On importing /soft + + + + + + + + + +

[Mageia-dev] On importing /soft

+ nicolas vigier + boklm at mars-attacks.org +
+ Wed Jan 19 21:47:12 CET 2011 +

+
+ +
On Wed, 19 Jan 2011, Pascal Terjan wrote:
+
+> http://svn.mageia.org/soft-cleaning/status.html#monitor-edid
+> says "- README: Some reference to the Mandriva mailing list and
+> bugzilla will need to be changed to Mageia ones"
+> 
+> Do we really want to?
+> What is the point?
+> I think we can package this tool as-is, as a tool provided by Mandriva
+> like if we were packaging a non distro specific tool developed by
+> RedHat or Debian or anyone and let people report their bugs upstream
+> if the README says so.
+> 
+> If someday it becomes unmaintained or for any other reason, we can
+> fork it, but currently I think of it as an external tool and see no
+> reason in importing it into our svn
+> 
+> I did not read the full list but I guess there are other standalone
+> tools that we don't need to fork into our svn.
+> 
+> Opinions?
+
+Yes, I agree. If it is not necessary to fork something (no proprietary
+images, no important and incompatible changes required) then we should
+not fork it until it becomes necessary.
+
+
+ + + + +
+

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