public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] manual: Fix up stdbit.texi
Date: Thu,  1 Feb 2024 15:40:50 +0000 (GMT)	[thread overview]
Message-ID: <20240201154050.D52DA38618AE@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c62b6265a641aaec4b0fa1b3fe622c2edf9c3821

commit c62b6265a641aaec4b0fa1b3fe622c2edf9c3821
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Feb 1 16:36:55 2024 +0100

    manual: Fix up stdbit.texi
    
    My recent change broke make pdf and in other documentation formats
    results in weird rendering and invalid URL, all because of a forgotten
    comma to separate @uref arguments.

Diff:
---
 manual/stdbit.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/manual/stdbit.texi b/manual/stdbit.texi
index f74d33903a..48591eab82 100644
--- a/manual/stdbit.texi
+++ b/manual/stdbit.texi
@@ -34,7 +34,7 @@ the functions but without any suffix such as @samp{_uc}.  The
 type-generic macro can only be used with an argument of an unsigned
 integer type with a width of 8, 16, 32 or 64 bits, or when using
 a compiler with support for
-@uref{https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html@code{__builtin_stdc_bit_ceil}},
+@uref{https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html,@code{__builtin_stdc_bit_ceil}},
 etc.@:, built-in functions such as GCC 14.1 or later
 any unsigned integer type those built-in functions support.
 In GCC 14.1 that includes support for @code{unsigned __int128} and

                 reply	other threads:[~2024-02-01 15:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240201154050.D52DA38618AE@sourceware.org \
    --to=jakub@sourceware.org \
    --cc=glibc-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).