[glib] gfile: More explicitly document the context for GFileProgressCallback

[Philip Withnall <pwithnall src gnome org>]

commit 9352cdb5f4f7dffa983d411625e874110b81cb35
Author: Philip Withnall <philip withnall collabora co uk>
Date:   Sat Apr 19 18:22:24 2014 +0100

    gfile: More explicitly document the context for GFileProgressCallback
    
    Be more explicit in the documentation for g_file_copy_async() about
    which GMainContext its progress callback is executed in.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=728565

 gio/gfile.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)
---
diff --git a/gio/gfile.c b/gio/gfile.c
index ae2dfb9..0da16c8 100644
--- a/gio/gfile.c
+++ b/gio/gfile.c
@@ -3402,8 +3402,9 @@ g_file_copy (GFile                  *source,
  * asynchronously. For details of the behaviour, see g_file_copy().
  *
  * If @progress_callback is not %NULL, then that function that will be called
- * just like in g_file_copy(), however the callback will run in the main loop,
- * not in the thread that is doing the I/O operation.
+ * just like in g_file_copy(). The callback will run in the default main context
+ * of the thread calling g_file_copy_async() — the same context as @callback is
+ * run in.
  *
  * When the operation is finished, @callback will be called. You can then call
  * g_file_copy_finish() to get the result of the operation.