diff options
author | dreid <dreid@13f79535-47bb-0310-9956-ffa450edef68> | 2004-06-15 10:27:58 +0000 |
---|---|---|
committer | dreid <dreid@13f79535-47bb-0310-9956-ffa450edef68> | 2004-06-15 10:27:58 +0000 |
commit | aab6cac59a649773ec96931ee1afe97269d7d16f (patch) | |
tree | 557f99db4ed9f562feb61c9c3762b9f3eb90d0b3 /STATUS | |
parent | 4cb6ddd22f411f46ab77ce123e7997ba6868812b (diff) | |
download | libapr-aab6cac59a649773ec96931ee1afe97269d7d16f.tar.gz |
Update STATUS
damn it's hot again.
git-svn-id: http://svn.apache.org/repos/asf/apr/apr/trunk@65201 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'STATUS')
-rw-r--r-- | STATUS | 14 |
1 files changed, 8 insertions, 6 deletions
@@ -1,5 +1,5 @@ APACHE PORTABLE RUNTIME (APR) LIBRARY STATUS: -*-text-*- -Last modified at [$Date: 2004/06/04 09:38:50 $] +Last modified at [$Date: 2004/06/15 10:27:58 $] Release: @@ -119,7 +119,7 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP: as apr_thread_exit(). See Message-Id: <E16JjZA-0007hg-00@zakath.apana.org.au> for thread discussing this. - +1: BrianH, Aaron + +1: BrianH, Aaron, david * Need some architecture/OS specific versions of the atomic operations. progress: generic, solaris Sparc, FreeBSD5, linux, and OS/390 done @@ -191,6 +191,8 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP: in the production code require more thought. Status: Sander Striker is looking into this (low priority) + David says this is a 1.1 issue. + * Deal with largefiles properly on those platforms that support it. Justin says: Linux refuses to have sendfile support and largefiles @@ -433,10 +435,10 @@ Stuff waiting for code thawing after Beta 1: (Not sure if the negatives would stay negative given that the change would now wait for the library versioning thing described above, though.) - Justin says: If you do this, please move it into apr-util where md5 - belongs! You'll have to address the random issue in - misc/unix/getuuid.c that forces md5 to be in APR. - Sander: +1 for the move. + + david: making the change for 1.0 should be safe. HTTPD 2.0.x will use + apr-0 which will have the apr_status_t return values. + +1 on the change. Stuff for post 1.0: |