Make sure all of the event loop API is marked with the proper version

Thu, 26 Oct 2023 05:45:33 -0500

author
Gary Kramlich <grim@reaperworld.com>
date
Thu, 26 Oct 2023 05:45:33 -0500
changeset 42424
ad55720b3b4d
parent 42423
5427e9f59cb7
child 42425
d1d0174ba72a

Make sure all of the event loop API is marked with the proper version

I compared these against a checkout of the v2.0.0 tag and using the girlint
stylesheet to verify.

Testing Done:
Asked the turtles for help.

Bugs closed: PIDGIN-17838

Reviewed at https://reviews.imfreedom.org/r/2724/

libpurple/eventloop.h file | annotate | diff | comparison | revisions
--- a/libpurple/eventloop.h	Thu Oct 26 05:40:14 2023 -0500
+++ b/libpurple/eventloop.h	Thu Oct 26 05:45:33 2023 -0500
@@ -37,6 +37,8 @@
  * @PURPLE_INPUT_WRITE: A write condition.
  *
  * An input condition.
+ *
+ * Since: 2.0.0
  */
 typedef enum
 {
@@ -55,6 +57,8 @@
  * purple_input_add().  The callback will receive the @user_data passed to
  * purple_input_add(), the file descriptor on which the event occurred, and the
  * condition that was satisfied to cause the callback to be invoked.
+ *
+ * Since: 2.0.0
  */
 typedef void (*PurpleInputFunction)(gpointer data, gint fd, PurpleInputCondition cond);
 
@@ -76,9 +80,11 @@
  * See g_io_add_watch_full().
  *
  * Returns: The resulting handle (will be greater than 0).
+ *
+ * Since: 2.0.0
  */
-guint purple_input_add(int fd, PurpleInputCondition cond,
-                       PurpleInputFunction func, gpointer user_data);
+PURPLE_AVAILABLE_IN_ALL
+guint purple_input_add(int fd, PurpleInputCondition cond, PurpleInputFunction func, gpointer user_data);
 
 /**
  * purple_input_pipe:

mercurial