luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-01-23 12:41:50 +01:00
Code Issues Packages Projects Releases Wiki Activity

gio: Fix several incorrect links in documentation comments

Browse Source 
Since commit 08f914b29, validation seems to have got a little
stricter/more correct.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>

Helps: #3037
This commit is contained in:
Philip Withnall 2023-11-15 13:53:00 +00:00
parent 552f62a059
commit bd33e0acd2
4 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
gio/gdrive.c
View File

@ -37,7 +37,7 @@
* It’s generally only created for removable hardware or hardware with
* removable media.
*
* `GDrive` is a container class for [class@Gio.Volume] objects that stem from
* `GDrive` is a container class for [iface@Gio.Volume] objects that stem from
* the same piece of media. As such, `GDrive` abstracts a drive with
* (or without) removable media and provides operations for querying
* whether media is available, determining whether media change is

4
gio/gmount.c
View File

@ -54,9 +54,9 @@
* [method@Gio.Mount.unmount_with_operation] with (at least) the `GMount`
* instance and a [type@Gio.AsyncReadyCallback]. The callback will be fired
* when the operation has resolved (either with success or failure), and a
* [struct@Gio.AsyncResult] structure will be passed to the callback. That
* [iface@Gio.AsyncResult] structure will be passed to the callback. That
* callback should then call [method@Gio.Mount.unmount_with_operation_finish]
* with the `GMount` and the [struct@Gio.AsyncResult] data to see if the
* with the `GMount` and the [iface@Gio.AsyncResult] data to see if the
* operation was completed successfully. If an `error` is present when
* [method@Gio.Mount.unmount_with_operation_finish] is called, then it will be
* filled with any error information.

2
gio/gsocketservice.c
View File

@ -47,7 +47,7 @@
*
* The socket service runs on the main loop of the
* thread-default context (see
* [method@GLib.MainContext.push_thread_default_context]) of the thread it is
* [method@GLib.MainContext.push_thread_default]) of the thread it is
* created in, and is not threadsafe in general. However, the calls to start and
* stop the service are thread-safe so these can be used from threads that
* handle incoming clients.

6
gio/gvolume.c
View File

@ -39,7 +39,7 @@
* `GVolume` is the moral equivalent of `GnomeVFSDrive`.
*
* Mounting a `GVolume` instance is an asynchronous operation. For more
* information about asynchronous operations, see [class@Gio.AsyncResult] and
* information about asynchronous operations, see [iface@Gio.AsyncResult] and
* [class@Gio.Task]. To mount a `GVolume`, first call [method@Gio.Volume.mount]
* with (at least) the `GVolume` instance, optionally a
* [class@Gio.MountOperation] object and a [type@Gio.AsyncReadyCallback].
@ -50,10 +50,10 @@
* for credentials.
*
* The callback will be fired when the operation has resolved (either
* with success or failure), and a [class@Gio.AsyncResult] instance will be
* with success or failure), and a [iface@Gio.AsyncResult] instance will be
* passed to the callback. That callback should then call
* [method@Gio.Volume.mount_finish] with the `GVolume` instance and the
* [class@Gio.AsyncResult] data to see if the operation was completed
* [iface@Gio.AsyncResult] data to see if the operation was completed
* successfully. If a [type@GLib.Error] is present when
* [method@Gio.Volume.mount_finish] is called, then it will be filled with any
* error information.