public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: <newlib@sourceware.org>, Jeff Johnston <jjohnstn@redhat.com>
Subject: Newlib's .texi docs - outdated version number/date
Date: Thu, 30 Mar 2023 09:28:15 +0200	[thread overview]
Message-ID: <2fb28796-c14d-e02a-a989-bbc0a7994399@codesourcery.com> (raw)

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.

I think it makes sense to bump the version + date of the two files for the release,
alongside the other version bumps done for the release. Namely, I think it should have
been part of the commit:
   commit 9e09d6ed83cce4777a5950412647ccc603040409 (tag: newlib-4.3.0)
   Bump up newlib to 4.3.0

Currently, there is the following (I think the first one is okayish
as it does not refer to the newlib version):

libgloss/doc/porting.texi
   @subtitle Spring 1995

newlib/libc/libc.texi
   @subtitle @code{libc} 2.5.0
   @subtitle December 2016

newlib/libm/libm.texi
   @subtitle @code{libm} 2.5.0
   @subtitle December 2016

The last textual change to libc was mid 2021, the last janitorial/re-org changes were
at the end of last year. Thus, blindly bumping the version/date seems to be at least more
consistent than not updating it at all.

Thoughts?

Tobias

PS: Namely, something like the following. (Ignoring (C) lines etc.)

--- a/newlib/libc/libc.texi
+++ b/newlib/libc/libc.texi
@@ -72,2 +72,2 @@ into another language, under the above conditions for modified versions.
-@subtitle @code{libc} 2.5.0
-@subtitle December 2016
+@subtitle @code{libc} 4.3.0
+@subtitle January 2023

--- a/newlib/libm/libm.texi
+++ b/newlib/libm/libm.texi
@@ -49,2 +49,2 @@ into another language, under the above conditions for modified versions.
-@subtitle @code{libm} 2.5.0
-@subtitle December 2016
+@subtitle @code{libm} 4.3.0
+@subtitle January 2023

-----------------
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

             reply	other threads:[~2023-03-30  7:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  7:28 Tobias Burnus [this message]
2023-03-30  9:07 ` Corinna Vinschen
2023-03-30  9:16   ` Tobias Burnus
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=2fb28796-c14d-e02a-a989-bbc0a7994399@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=jjohnstn@redhat.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).