svn commit: r1935567 - apr/apr/trunk

Author: dsahlberg
Date: Tue Jun 23 07:30:54 2026
New Revision: 1935567

Log:
* STATUS
  Trim trailing witespace - follow what .editorconfig says we do

Modified:
   apr/apr/trunk/STATUS

Modified: apr/apr/trunk/STATUS
==============================================================================
--- apr/apr/trunk/STATUS	Tue Jun 23 06:45:03 2026	(r1935566)
+++ apr/apr/trunk/STATUS	Tue Jun 23 07:30:54 2026	(r1935567)
@@ -290,7 +290,7 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE RE
 
     * FirstBill says we need a new procattr, APR_CREATE_SUSPENDED (or
       something similar) to direct ap_create_process to create the
-      process suspended. We also need a call to wake up the suspended 
+      process suspended. We also need a call to wake up the suspended
       process.  This may not be able to be implemented everywhere though.
         Status: OtherBill asks, why?  What is the benefit, how is it
         portably implemented?  Unless this creates some tangible that
@@ -316,7 +316,7 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE RE
       sendfile implementation.
 
       david: The socket options stuff is now in and using it should
-             reduce the number of syscalls that are required for 
+             reduce the number of syscalls that are required for
              os_cork and uncork, so the code should be reviewed to
              make use of the new calls.  If no-one beats me to it I'll
              get around to it soonish...
@@ -339,23 +339,23 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE RE
     * need to export (in code, not just build scripts) the shared
       library extension (e.g. ".so") for the platform. clients need to
       use this to construct filenames to pass to apr_dso_load()
-      -- note on Win32 we distinguish 'apache module' names from other 
+      -- note on Win32 we distinguish 'apache module' names from other
          'loadable module' names, so be careful with Apache's directive.
          AIX, HPUX may use similar (.so for a 'module's name while the
          defaults .a or .sl are used for libs.)
 
     * Possible gmtime_r replacement in explode_time
       On Solaris (and possibly others), the gmtime_r libc function obtains
-      a mutex.  We have seen 21/25 threads being blocked in this mutex on 
-      a threaded httpd MPM when requesting static pages.  It may be worth 
-      it to hand optimize this since there is no real need for a mutex at 
-      the system level (straight arithmetic from what I can tell).  If you 
+      a mutex.  We have seen 21/25 threads being blocked in this mutex on
+      a threaded httpd MPM when requesting static pages.  It may be worth
+      it to hand optimize this since there is no real need for a mutex at
+      the system level (straight arithmetic from what I can tell).  If you
       have access to the Solaris source code:
         osnet_volume/usr/src/lib/libc/port/gen/time_comm.c.
 
-    * Add a way to query APR for what features it has at runtime (i.e. 
+    * Add a way to query APR for what features it has at runtime (i.e.
       threads).
-      Justin says: I'm not completely sold on this, but it has been mentioned 
+      Justin says: I'm not completely sold on this, but it has been mentioned
                    before and at least added to STATUS.
 
     * apr_xlate.h generates a bunch of compiler warnings.
@@ -368,10 +368,10 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE RE
       httpd (prefork MPM) error log says (predictably):
 
       (46)No record locks available: couldn't grab the accept mutex
- 
-      All of the children report this and subsequently exits.  httpd is now 
+
+      All of the children report this and subsequently exits.  httpd is now
       hosed.  AFAICT, this does not look to be an out-of-fds error.
- 
+
       Solaris's man page says:
         ENOLCK
            The  cmd argument is F_SETLK, F_SETLK64, F_SETLKW,  or
@@ -416,9 +416,9 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE RE
     * Once we are fully satisfied with the new lock API, we can
       begin to migrate the old API to be implemented on top of the
       new one, or just decide to get rid of it altogether.
-      
+
     * FreeBSD returns 45 (EOPNOTSUPP) when the lockfile is on a NFS
-      partition when you call fcntl(F_SETLKW).  It may be good if we 
+      partition when you call fcntl(F_SETLKW).  It may be good if we
       can somehow detect this and error out when creating the lock
       rather than waiting for the error to occur when acquiring lock.
 
@@ -436,7 +436,7 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE RE
       See OtherBill's comments in this message to [email protected]:
       Message-Id: <5.1.0.14.2.20020315080852.00bce168@localhost>
 
-    * Identify and implement those protection bits that have general 
+    * Identify and implement those protection bits that have general
         usefulness, perhaps hidden, generic read-only [immutable],
         effective current user permissions, etc.
 
@@ -474,7 +474,7 @@ Interface Changes Postponed for APR 2.0:
 
     * possible type renames:
 
-        apr_file_info_t                  from apr_finfo_t 
+        apr_file_info_t                  from apr_finfo_t
         apr_file_attrs_t                 from apr_fileattrs_t
         apr_file_seek_where_t            from apr_seek_where_t
         apr_lock_mech_e                  from apr_lockmech_e
@@ -500,13 +500,13 @@ Interface Changes Postponed for APR 2.0:
       application calls apr_proc_wait[_all_procs]() and is given back
       apr_exit_why_e and exit_code_or_signal_num, thus losing the original
       (on Unix, at least) representation which held both pieces of information
-      in an int.  Both pieces of data should be available to the maintenance 
+      in an int.  Both pieces of data should be available to the maintenance
       function so that it has the opportunity to take different actions.  An
       example would be to issue messages about probable misconfiguration when
-      receiving a certain exit code and trying to restart otherwise.  Thus, 
-      apr_proc_other_child_alert() should take an additional apr_exit_why_e 
-      parameter, as should the application-provided maintenance function.  The 
-      exit-why value would be ignored in the same circumstances as the existing 
+      receiving a certain exit code and trying to restart otherwise.  Thus,
+      apr_proc_other_child_alert() should take an additional apr_exit_why_e
+      parameter, as should the application-provided maintenance function.  The
+      exit-why value would be ignored in the same circumstances as the existing
       status parameter: reason != APR_OC_REASON_DEATH.
 
     * apr_file_gets() should take an apr_size_t size parameter?
@@ -515,7 +515,7 @@ Interface Changes Postponed for APR 2.0:
       list once the callback function returns non-zero; see JCW's
       comment in apr_tables.c.
 
-    * The library SONAME should vary for the different library ABIs - 
+    * The library SONAME should vary for the different library ABIs -
       i.e. LFS support, IPv6 support or not.
 
     * remove APR_POLL_LASTDESC from apr_datatype_e.
@@ -561,5 +561,3 @@ Interface Changes Postponed for APR 2.0:
       discussing this.
         +1: BrianH, Aaron, david, jerenkrantz
       Status: Deferred to 2.0.0 (API change)
-
-