Author: aurel32
Date: 2010-05-24 16:53:38 +0000 (Mon, 24 May 2010)
New Revision: 4284

Modified:
   glibc-package/branches/eglibc-2.11/debian/changelog
   glibc-package/branches/eglibc-2.11/debian/patches/series
Log:
  * Add debian/patches/any/cvs-umount-nofollow.diff from upstream to define
    UMOUNT_NOFOLLOW.



Modified: glibc-package/branches/eglibc-2.11/debian/changelog
===================================================================
--- glibc-package/branches/eglibc-2.11/debian/changelog 2010-05-24 16:51:52 UTC 
(rev 4283)
+++ glibc-package/branches/eglibc-2.11/debian/changelog 2010-05-24 16:53:38 UTC 
(rev 4284)
@@ -79,6 +79,8 @@
   * Explictely call /sbin/start-stop-daemon in nscd.init.  Closes: bug#575404.
   * Add debian/patches/any/cvs-getaddrinfo.diff from upstream to not abort
     the getaddrinfo loop on the first successful.
+  * Add debian/patches/any/cvs-umount-nofollow.diff from upstream to define
+    UMOUNT_NOFOLLOW.
 
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/submitted-rtld_lock_recursive.diff: New patch to
@@ -95,7 +97,7 @@
   * Add kfreebsd/local-dosavesse.diff, which does not work,
     so rather use also added kfreebsd/local-nosavesse.diff
 
- -- Aurelien Jarno <[email protected]>  Mon, 24 May 2010 18:45:18 +0200
+ -- Aurelien Jarno <[email protected]>  Mon, 24 May 2010 18:53:06 +0200
 
 eglibc (2.10.2-9) unstable; urgency=low
 

Modified: glibc-package/branches/eglibc-2.11/debian/patches/series
===================================================================
--- glibc-package/branches/eglibc-2.11/debian/patches/series    2010-05-24 
16:51:52 UTC (rev 4283)
+++ glibc-package/branches/eglibc-2.11/debian/patches/series    2010-05-24 
16:53:38 UTC (rev 4284)
@@ -229,3 +229,4 @@
 any/submitted-nptl-invalid-td.patch
 any/local-gai-rfc1918-scope-global.patch
 any/cvs-getaddrinfo.diff
+any/cvs-umount-nofollow.diff


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]

Reply via email to