public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: <newlib@sourceware.org>
Subject: Re: Newlib's .texi docs - outdated version number/date
Date: Thu, 30 Mar 2023 11:16:07 +0200	[thread overview]
Message-ID: <d353c75f-252c-996d-aa08-b632c29ef577@codesourcery.com> (raw)
In-Reply-To: <ZCVRYtl83EoYZA+c@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

On 30.03.23 11:07, Corinna Vinschen wrote:
> On Mar 30 09:28, Tobias Burnus wrote:
>> Someone over here stumbled over the version/date mismatch between what is shown
>> in the libc/libm manuals - and what is the current newlib release.
>> ...
>> ... Thus, blindly bumping the version/date seems to be at least more
>> consistent than not updating it at all.
>>
>> Thoughts?
> Sounds good.  Please send a patch in git format-patch style.

Done now.

Thanks,

Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

[-- Attachment #2: 0001-Bump-newlib-version-in-the-manual-to-4.3.0.patch --]
[-- Type: text/x-patch, Size: 1487 bytes --]

From 78aa011af1d1ce18b3a60056d39dcf331f4fe625 Mon Sep 17 00:00:00 2001
From: Tobias Burnus <tobias@codesourcery.com>
Date: Thu, 30 Mar 2023 11:09:33 +0200
Subject: [PATCH] Bump newlib version in the manual to 4.3.0

While commit 9e09d6ed8 (tag: newlib-4.3.0) bumped the newlib version to 4.3.0,
this commit updates the version/date in the libc/libm manuals to match.
---
 newlib/libc/libc.texi | 4 ++--
 newlib/libm/libm.texi | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/newlib/libc/libc.texi b/newlib/libc/libc.texi
index 72328e148..acb6afb5b 100644
--- a/newlib/libc/libc.texi
+++ b/newlib/libc/libc.texi
@@ -69,8 +69,8 @@ into another language, under the above conditions for modified versions.
 @title The Red Hat newlib C Library
 @subtitle Full Configuration
 @sp 1
-@subtitle @code{libc} 2.5.0
-@subtitle December 2016
+@subtitle @code{libc} 4.3.0
+@subtitle January 2023
 @author {Steve Chamberlain}
 @author {Roland Pesch}
 @author {Red Hat Support}
diff --git a/newlib/libm/libm.texi b/newlib/libm/libm.texi
index 779615d32..d3ca9ae3c 100644
--- a/newlib/libm/libm.texi
+++ b/newlib/libm/libm.texi
@@ -46,8 +46,8 @@ into another language, under the above conditions for modified versions.
 @titlepage
 @title The Red Hat newlib C Math Library
 @sp 1
-@subtitle @code{libm} 2.5.0
-@subtitle December 2016
+@subtitle @code{libm} 4.3.0
+@subtitle January 2023
 @author {Steve Chamberlain}
 @author {Roland Pesch}
 @author {Red Hat Support}
-- 
2.34.1


  reply	other threads:[~2023-03-30  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  7:28 Tobias Burnus
2023-03-30  9:07 ` Corinna Vinschen
2023-03-30  9:16   ` Tobias Burnus [this message]
2023-03-30 12:11     ` Corinna Vinschen
2023-04-05 15:53       ` Brian Inglis

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=d353c75f-252c-996d-aa08-b632c29ef577@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=newlib@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).