summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoland McGrath <roland@gnu.org>1996-07-27 00:40:06 +0000
committerRoland McGrath <roland@gnu.org>1996-07-27 00:40:06 +0000
commit7443a5a8a410a02d0e8f6894369ae27d934e5177 (patch)
tree7480d51ce6d3fcb53ea5476566ceb5073d830506 /PROJECTS
parentFri Jul 26 00:36:50 1996 Roland McGrath <roland@delasyd.gnu.ai.mit.edu> (diff)
downloadglibc-7443a5a8a410a02d0e8f6894369ae27d934e5177.tar.gz
glibc-7443a5a8a410a02d0e8f6894369ae27d934e5177.tar.bz2
glibc-7443a5a8a410a02d0e8f6894369ae27d934e5177.zip
Fri Jul 26 20:39:42 1996 Roland McGrath <roland@delasyd.gnu.ai.mit.edu>
* ctype/test_ctype.c: Test EOF too.
Diffstat (limited to 'PROJECTS')
-rw-r--r--PROJECTS12
1 files changed, 6 insertions, 6 deletions
diff --git a/PROJECTS b/PROJECTS
index 4c755ff8dd..03cd0192ac 100644
--- a/PROJECTS
+++ b/PROJECTS
@@ -1,6 +1,6 @@
Open jobs for finishing GNU libc:
---------------------------------
-Status: June 1996
+Status: July 1996
If you have time and talent to take over any of the jobs below please
contact <bug-glibc@prep.ai.mit.edu>
@@ -32,7 +32,7 @@ contact <bug-glibc@prep.ai.mit.edu>
Implementation idea: use some functions from bash.
-[ 5] Write reentrent versions of crypt() et.al.
+[ 5] Write reentrant versions of crypt() et.al.
Implementation idea: Define in <crypt.h>
@@ -51,7 +51,7 @@ contact <bug-glibc@prep.ai.mit.edu>
void encrypt_r (char *__block, int __edflag,
struct crypt_data *__data);
- If possible the non-reentrent functions should use the reentrent
+ If possible the non-reentrant functions should use the reentrant
ones.
Because of the US export restrictions it might be a good idea if
@@ -108,8 +108,8 @@ contact <bug-glibc@prep.ai.mit.edu>
contribute it to the FSF.
-[13] Write access function for ether, shadow, netmasks, bootparams,
- netgroup, publickey, automount, aliases databases for nss_files
- and nss_db module.
+[13] Write access function for shadow, netmasks, bootparams, netgroup,
+ publickey, automount, aliases databases for nss_files and nss_db
+ module.
The functions should be embedded in the nss scheme. This is not
hard and not all services must be supported at once.