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/20110209/002505.html | 73 +++++++++++++++++++++++++++++++++ 1 file changed, 73 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110209/002505.html (limited to 'zarb-ml/mageia-dev/20110209/002505.html') diff --git a/zarb-ml/mageia-dev/20110209/002505.html b/zarb-ml/mageia-dev/20110209/002505.html new file mode 100644 index 000000000..6f2820c53 --- /dev/null +++ b/zarb-ml/mageia-dev/20110209/002505.html @@ -0,0 +1,73 @@ + + + + [Mageia-dev] 26/01/2011 meeting + + + + + + + + + +

[Mageia-dev] 26/01/2011 meeting

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Feb 9 09:22:25 CET 2011 +

+
+ +
On 8 February 2011 23:22, Ahmad Samir <ahmadsamir3891 at gmail.com> wrote:
+>>> Personally, as I said before about upstreaming patches, I don't think
+>>> I have enough experience to judge if a patch should go upstream or
+>>> not, so that part I can't do.
+>>>
+>>> What do you mean by "commented"?
+>>
+>> A thing like:
+>>
+>> #patch from .... to fix truc
+>> Patch0: glibc-2.12-truc.fix.patch
+>>
+>
+> That's usually available in the svn log, whoever wrote the patch
+> should have commented it if that is the policy, however I am not aware
+> that such a policy exists (IMBW though).
+
+remember we lost Mdv history when importing packages?
+(SILENT stuff, ...)
+
+ + + +
+

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