Author: jim
Date: 2005-07-06 14:23:43 -0600 (Wed, 06 Jul 2005)
New Revision: 1006

Added:
   trunk/linux-libc-headers/linux-libc-headers-2.6.12.2-sparc_biarch-1.patch
   trunk/linux-libc-headers/linux-libc-headers-2.6.12.2-x86_64_biarch-1.patch
Modified:
   trunk/
Log:
 [EMAIL PROTECTED]:  jim | 2005-07-06 13:18:18 -0700
 Updated biarch patches



Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - cc2644d5-6cf8-0310-b111-c40428001e49:/patches:1039
   + cc2644d5-6cf8-0310-b111-c40428001e49:/patches:1044

Added: trunk/linux-libc-headers/linux-libc-headers-2.6.12.2-sparc_biarch-1.patch
===================================================================
--- trunk/linux-libc-headers/linux-libc-headers-2.6.12.2-sparc_biarch-1.patch   
2005-07-06 18:22:14 UTC (rev 1005)
+++ trunk/linux-libc-headers/linux-libc-headers-2.6.12.2-sparc_biarch-1.patch   
2005-07-06 20:23:43 UTC (rev 1006)
@@ -0,0 +1 @@
+link linux-libc-headers-2.6.11.2-sparc_biarch-1.patch
\ No newline at end of file


Property changes on: 
trunk/linux-libc-headers/linux-libc-headers-2.6.12.2-sparc_biarch-1.patch
___________________________________________________________________
Name: svn:special
   + *

Added: 
trunk/linux-libc-headers/linux-libc-headers-2.6.12.2-x86_64_biarch-1.patch
===================================================================
--- trunk/linux-libc-headers/linux-libc-headers-2.6.12.2-x86_64_biarch-1.patch  
2005-07-06 18:22:14 UTC (rev 1005)
+++ trunk/linux-libc-headers/linux-libc-headers-2.6.12.2-x86_64_biarch-1.patch  
2005-07-06 20:23:43 UTC (rev 1006)
@@ -0,0 +1 @@
+link linux-libc-headers-2.6.11.2-x86_64_biarch-2.patch
\ No newline at end of file


Property changes on: 
trunk/linux-libc-headers/linux-libc-headers-2.6.12.2-x86_64_biarch-1.patch
___________________________________________________________________
Name: svn:special
   + *

-- 
http://linuxfromscratch.org/mailman/listinfo/patches
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to