From: Josef Wolf <jw@raven.inka.de>
To: newlib@sourceware.org
Subject: Confusion about version numbering scheme
Date: Thu, 11 Jun 2020 11:31:06 +0200 [thread overview]
Message-ID: <20200611093106.GC15174@raven.inka.de> (raw)
Hello all,
in order to find out details for
https://sourceware.org/pipermail/newlib/2020/017688.html
I decided to git-bisect newlib-3.1.0 up to newlib-3.2.0.
And on that, I'm somewhat confused about newlib version numbering scheme.
How comes that cygwin-3_0-branch and cygwin-3_0_x-release are SUCCESSORS of
newlib-3.1.0 tag?
Thbis makes me wonder whether
ftp://sourceware.org/pub/newlib/newlib-3.1.0.tar.gz was really created from
the newlib-3.1.0 tag?
--
Josef Wolf
jw@raven.inka.de
next reply other threads:[~2020-06-11 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 9:31 Josef Wolf [this message]
2020-06-11 17:30 ` Jeff Johnston
2020-06-11 17:41 ` Yaakov Selkowitz
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=20200611093106.GC15174@raven.inka.de \
--to=jw@raven.inka.de \
--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).