From cfd2ea50475529df407eb83b8e3562abf74c1c59 Mon Sep 17 00:00:00 2001 From: Joseph Myers Date: Wed, 25 Jun 2014 12:55:21 +0000 Subject: [PATCH] Update README and NEWS for ports directory removal. This patch updates README to remove a mention of the ports directory. It also adds a NEWS item for the merge of ports into the main sysdeps tree (I think it's NEWS-worthy, although not strictly a user-visible feature). Other remaining ports references to resolve: a comment in manual/signal.texi (not giving a literal path, but maybe should change anyway); a comment in config.h.in (path should be updated); scripts/list-sources.sh (appears to date back to ports being a separate repository). * README: Do not mention ports directory. --- ChangeLog | 2 ++ NEWS | 4 ++++ README | 4 ---- 3 files changed, 6 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index d151410..b730c09 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,7 @@ 2014-06-25 Joseph Myers + * README: Do not mention ports directory. + * sysdeps/unix/sysv/linux/kernel-features.h (__ASSUME_UTIMENSAT): Remove macro. * sysdeps/unix/sysv/linux/futimes.c: Do not include diff --git a/NEWS b/NEWS index 3ddbec1..e854c251 100644 --- a/NEWS +++ b/NEWS @@ -61,6 +61,10 @@ Version 2.20 deference a dangling pointer, or use an unexpected pathname argument if the string was modified after the posix_spawn_file_actions_addopen invocation. + +* All supported architectures now use the main glibc sysdeps directory + instead of some being in a separate "ports" directory (which was + distributed separately before glibc 2.17). Version 2.19 diff --git a/README b/README index 3743241..ce7d103 100644 --- a/README +++ b/README @@ -45,10 +45,6 @@ The GNU C Library supports these configurations for using Linux kernels: tilegx-*-linux-gnu tilepro-*-linux-gnu -The code for other CPU configurations supported by volunteers outside of -the core glibc maintenance effort is contained in the `ports' add-on, -located in the `ports' subdirectory of the source tree. - If you are interested in doing a port, please contact the glibc maintainers; see http://www.gnu.org/software/libc/ for more information. -- 2.7.4