From: Yaakov Selkowitz <yselkowi@redhat.com>
To: Newlib <newlib@sourceware.org>
Subject: Re: Confusion about version numbering scheme
Date: Thu, 11 Jun 2020 13:41:15 -0400 [thread overview]
Message-ID: <7da7b3745dbb3b9e3a389158cd458c4e60c9bcd8.camel@redhat.com> (raw)
In-Reply-To: <CAOox84uQ6nAfHZc74R=rEOJp5FpLDUXC9+snPH8+Owmr6eDQ5Q@mail.gmail.com>
On Thu, 2020-06-11 at 13:30 -0400, Jeff Johnston via Newlib wrote:
> The newlib tag gets created by a shell script I run which at the same time
> creates the archive and uploads it.
>
> I can't speak as to why the cygwin tags are the way they are and Corinna is
> on vacation at the moment, but perhaps
> one of the other Cygwin maintainers can comment.
Simple: Cygwin's version numbering is completely independent of
Newlib's.
> On Thu, Jun 11, 2020 at 5:40 AM Josef Wolf <jw@raven.inka.de> wrote:
>
> > 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?
--
Yaakov Selkowitz
Senior Software Engineer - Platform Enablement
Red Hat, Inc.
prev parent reply other threads:[~2020-06-11 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 9:31 Josef Wolf
2020-06-11 17:30 ` Jeff Johnston
2020-06-11 17:41 ` Yaakov Selkowitz [this message]
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=7da7b3745dbb3b9e3a389158cd458c4e60c9bcd8.camel@redhat.com \
--to=yselkowi@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).