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

[Mageia-dev] 26/01/2011 meeting

+ Ahmad Samir + ahmadsamir3891 at gmail.com +
+ Tue Feb 8 23:22:59 CET 2011 +

+
+ +
On 8 February 2011 08:21, Cazzaniga Sandro <cazzaniga.sandro at gmail.com> wrote:
+> Le 07/02/2011 22:11, Ahmad Samir a écrit :
+>>
+>> 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).
+
+-- 
+Ahmad Samir
+
+ + +
+

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