mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-08-02 15:33:39 +02:00
minor typos in the documentation (a/an)
This commit is contained in:
@@ -361,7 +361,7 @@ G_STMT_START { \
|
||||
*
|
||||
* @param[in,out] removed A list of the removed files in the directory.
|
||||
* @param[in,out] added A list of the added files of the directory.
|
||||
* @param[in] cbs A pointer to #traverse_cbs, an user-defined set of
|
||||
* @param[in] cbs A pointer to #traverse_cbs, a user-defined set of
|
||||
* traverse callbacks.
|
||||
* @param[in] udata A pointer to the user-defined data.
|
||||
* @return 0 if no files were renamed, >0 otherwise.
|
||||
@@ -402,7 +402,7 @@ dl_detect_moves (dep_list **removed,
|
||||
*
|
||||
* @param[in,out] removed A list of the removed files in the directory.
|
||||
* @param[in,out] current A list with the current contents of the directory.
|
||||
* @param[in] cbs A pointer to #traverse_cbs, an user-defined set of
|
||||
* @param[in] cbs A pointer to #traverse_cbs, a user-defined set of
|
||||
* traverse callbacks.
|
||||
* @param[in] udata A pointer to the user-defined data.
|
||||
* @return 0 if no files were renamed, >0 otherwise.
|
||||
@@ -447,7 +447,7 @@ dl_detect_replacements (dep_list **removed,
|
||||
*
|
||||
* @param[in,out] previous A list with the previous contents of the directory.
|
||||
* @param[in,out] current A list with the current contents of the directory.
|
||||
* @param[in] cbs A pointer to #traverse_cbs, an user-defined set of
|
||||
* @param[in] cbs A pointer to #traverse_cbs, a user-defined set of
|
||||
* traverse callbacks.
|
||||
* @param[in] udata A pointer to the user-defined data.
|
||||
* @return 0 if no files were renamed, >0 otherwise.
|
||||
|
@@ -265,7 +265,7 @@ g_kqueue_file_monitor_start (GLocalFileMonitor *local_monitor,
|
||||
/* For a directory monitor, create a subscription object anyway.
|
||||
* It will be used for directory diff calculation routines.
|
||||
* Wait, directory diff in a GKqueueFileMonitor?
|
||||
* Yes, it is. When a file monitor is started on an non-existent
|
||||
* Yes, it is. When a file monitor is started on a non-existent
|
||||
* file, GIO uses a GKqueueFileMonitor object for that. If a directory
|
||||
* will be created under that path, GKqueueFileMonitor will have to
|
||||
* handle the directory notifications. */
|
||||
|
Reference in New Issue
Block a user