From: Matthias Clasen Date: Mon, 3 Oct 2011 02:38:49 +0000 (-0400) Subject: Fix doc build X-Git-Tag: 2.31.0~283 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=65b84bb7d0e429a30f344ebc149dc3d8d79bddda;p=platform%2Fupstream%2Fglib.git Fix doc build The markup here was not only broken, it was also unnecessary, since gtk-doc knows to apply tags to things that end with () already. --- diff --git a/glib/gthread-posix.c b/glib/gthread-posix.c index c47fc0d..51b886d 100644 --- a/glib/gthread-posix.c +++ b/glib/gthread-posix.c @@ -866,17 +866,15 @@ g_cond_timedwait (GCond *cond, * GPrivate: * * The #GPrivate struct is an opaque data structure to represent a - * thread-local data key. It is approximately equivalent to the - * pthread_setspecific()/pthread_getspecific() - * APIs on POSIX and to - * TlsSetValue()/TlsGetValue<()/function> on - * Windows. + * thread-local data key. It is approximately equivalent to the + * pthread_setspecific()/pthread_getspecific() APIs on POSIX and to + * TlsSetValue()/TlsGetValue() on Windows. * - * If you don't already know why you might want this functionality, then - * you probably don't need it. + * If you don't already know why you might want this functionality, + * then you probably don't need it. * * #GPrivate is a very limited resource (as far as 128 per program, - * shared between all libraries). It is also not possible to destroy a + * shared between all libraries). It is also not possible to destroy a * #GPrivate after it has been used. As such, it is only ever acceptable * to use #GPrivate in static scope, and even then sparingly so. *