Hi,

Apologies if there is a different mailing list for this, I could not find one.

Recently did a spelling / typo check within our project and found some in libev.  Went ahead and fixed them and a few others I found within libev's repo.  Patch is attached.

Thanks,

Al

--
Albert Chu
Livermore Computing
Lawrence Livermore National Laboratory
Index: README
===================================================================
RCS file: /schmorpforge/libev/README,v
retrieving revision 1.23
diff -u -r1.23 README
--- README	26 Jun 2021 16:24:25 -0000	1.23
+++ README	7 Apr 2023 18:28:15 -0000
@@ -9,7 +9,7 @@
                 http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
    Library Documentation: http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod
 
-   Libev is modelled (very losely) after libevent and the Event perl
+   Libev is modelled (very loosely) after libevent and the Event perl
    module, but is faster, scales better and is more correct, and also more
    featureful. And also smaller. Yay.
 
Index: ev.3
===================================================================
RCS file: /schmorpforge/libev/ev.3,v
retrieving revision 1.124
diff -u -r1.124 ev.3
--- ev.3	9 May 2021 18:41:06 -0000	1.124
+++ ev.3	7 Apr 2023 18:28:16 -0000
@@ -4423,7 +4423,7 @@
 clashing with the \f(CW\*(C`set (loop)\*(C'\fR method.
 .Sp
 For \f(CW\*(C`ev::io\*(C'\fR watchers there is an additional \f(CW\*(C`set\*(C'\fR method that acepts a
-new event mask only, and internally calls \f(CW\*(C`ev_io_modfify\*(C'\fR.
+new event mask only, and internally calls \f(CW\*(C`ev_io_modify\*(C'\fR.
 .IP "w\->start ()" 4
 .IX Item "w->start ()"
 Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the
Index: ev.c
===================================================================
RCS file: /schmorpforge/libev/ev.c,v
retrieving revision 1.536
diff -u -r1.536 ev.c
--- ev.c	10 Aug 2022 16:50:05 -0000	1.536
+++ ev.c	7 Apr 2023 18:28:16 -0000
@@ -2398,7 +2398,7 @@
 {
   int i;
 
-  /* most backends do not modify the fdchanges list in backend_modfiy.
+  /* most backends do not modify the fdchanges list in backend_modify.
    * except io_uring, which has fixed-size buffers which might force us
    * to handle events in backend_modify, causing fdchanges to be amended,
    * which could result in an endless loop.
@@ -3510,7 +3510,7 @@
   if (postfork != 2)
     {
       #if EV_USE_SIGNALFD
-        /* surprisingly, nothing needs to be done for signalfd, accoridng to docs, it does the right thing on fork */
+        /* surprisingly, nothing needs to be done for signalfd, according to docs, it does the right thing on fork */
       #endif
       
       #if EV_USE_TIMERFD
Index: ev.pod
===================================================================
RCS file: /schmorpforge/libev/ev.pod,v
retrieving revision 1.467
diff -u -r1.467 ev.pod
--- ev.pod	13 Sep 2020 22:17:02 -0000	1.467
+++ ev.pod	7 Apr 2023 18:28:16 -0000
@@ -4270,7 +4270,7 @@
 clashing with the C<set (loop)> method.
 
 For C<ev::io> watchers there is an additional C<set> method that acepts a
-new event mask only, and internally calls C<ev_io_modfify>.
+new event mask only, and internally calls C<ev_io_modify>.
 
 =item w->start ()
 
Index: ev_iouring.c
===================================================================
RCS file: /schmorpforge/libev/ev_iouring.c,v
retrieving revision 1.26
diff -u -r1.26 ev_iouring.c
--- ev_iouring.c	10 Aug 2022 16:50:05 -0000	1.26
+++ ev_iouring.c	7 Apr 2023 18:28:16 -0000
@@ -67,7 +67,7 @@
  *    later versions not only bump this to 32k, but also can handle
  *    an unlimited amount of events, so this only affects the batch size.
  * i) unlike linux aio, you *can* register more then the limit
- *    of fd events. while early verisons of io_uring signalled an overflow
+ *    of fd events. while early versions of io_uring signalled an overflow
  *    and you ended up getting wet. 5.5+ does not do this anymore.
  * j) but, oh my! it had exactly the same bugs as the linux aio backend,
  *    where some undocumented poll combinations just fail. fortunately,
Index: ev_linuxaio.c
===================================================================
RCS file: /schmorpforge/libev/ev_linuxaio.c,v
retrieving revision 1.53
diff -u -r1.53 ev_linuxaio.c
--- ev_linuxaio.c	27 Dec 2019 16:12:55 -0000	1.53
+++ ev_linuxaio.c	7 Apr 2023 18:28:16 -0000
@@ -93,7 +93,7 @@
 
 #include <sys/syscall.h> /* no glibc wrappers */
 
-/* aio_abi.h is not versioned in any way, so we cannot test for its existance */
+/* aio_abi.h is not versioned in any way, so we cannot test for its existence */
 #define IOCB_CMD_POLL 5
 
 /* taken from linux/fs/aio.c. yup, that's a .c file.
Index: import_libevent
===================================================================
RCS file: /schmorpforge/libev/import_libevent,v
retrieving revision 1.29
diff -u -r1.29 import_libevent
--- import_libevent	15 Apr 2008 04:34:07 -0000	1.29
+++ import_libevent	7 Apr 2023 18:28:16 -0000
@@ -3,7 +3,7 @@
 LE=../libevent-1.4.3-stable
 
 if ! [ -e evbuffer.c ]; then
-   echo do not run this programm unless you know what you are doing
+   echo do not run this program unless you know what you are doing
    exit 1
 fi
 
_______________________________________________
libev mailing list
libev@lists.schmorp.de
http://lists.schmorp.de/mailman/listinfo/libev

Reply via email to