public inbox for newlib-cvs@sourceware.org help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@sourceware.org> To: newlib-cvs@sourceware.org Subject: [newlib-cygwin] Remove curly braces in `@author` tag in .texi files Date: Tue, 19 Dec 2023 18:28:46 +0000 (GMT) [thread overview] Message-ID: <20231219182846.802DD385840D@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=60c6397133b741a532579670929dbf47e25fbd31 commit 60c6397133b741a532579670929dbf47e25fbd31 Author: Freddie Chopin <freddie.chopin@gmail.com> Date: Sun Dec 17 10:01:45 2023 +0100 Remove curly braces in `@author` tag in .texi files Curly braces cause documentation build failure with texinfo 7.1 (works fine up to 7.0.3): Diff: --- newlib/libc/libc.texi | 8 ++++---- newlib/libm/libm.texi | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/newlib/libc/libc.texi b/newlib/libc/libc.texi index acb6afb5b..a5f24b15a 100644 --- a/newlib/libc/libc.texi +++ b/newlib/libc/libc.texi @@ -71,10 +71,10 @@ into another language, under the above conditions for modified versions. @sp 1 @subtitle @code{libc} 4.3.0 @subtitle January 2023 -@author {Steve Chamberlain} -@author {Roland Pesch} -@author {Red Hat Support} -@author {Jeff Johnston} +@author Steve Chamberlain +@author Roland Pesch +@author Red Hat Support +@author Jeff Johnston @page @tex diff --git a/newlib/libm/libm.texi b/newlib/libm/libm.texi index d3ca9ae3c..bf8a07255 100644 --- a/newlib/libm/libm.texi +++ b/newlib/libm/libm.texi @@ -48,10 +48,10 @@ into another language, under the above conditions for modified versions. @sp 1 @subtitle @code{libm} 4.3.0 @subtitle January 2023 -@author {Steve Chamberlain} -@author {Roland Pesch} -@author {Red Hat Support} -@author {Jeff Johnston} +@author Steve Chamberlain +@author Roland Pesch +@author Red Hat Support +@author Jeff Johnston @page @tex
reply other threads:[~2023-12-19 18:28 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=20231219182846.802DD385840D@sourceware.org \ --to=jjohnstn@sourceware.org \ --cc=newlib-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: linkBe 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).