From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) by sourceware.org (Postfix) with ESMTP id E6D1E383F859 for ; Thu, 11 Jun 2020 17:41:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E6D1E383F859 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-391-NHO8ILeBOoahgnfIVAynbg-1; Thu, 11 Jun 2020 13:41:18 -0400 X-MC-Unique: NHO8ILeBOoahgnfIVAynbg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9839B1005512 for ; Thu, 11 Jun 2020 17:41:17 +0000 (UTC) Received: from ovpn-112-211.rdu2.redhat.com (ovpn-112-211.rdu2.redhat.com [10.10.112.211]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4D01160BF4 for ; Thu, 11 Jun 2020 17:41:16 +0000 (UTC) Message-ID: <7da7b3745dbb3b9e3a389158cd458c4e60c9bcd8.camel@redhat.com> Subject: Re: Confusion about version numbering scheme From: Yaakov Selkowitz To: Newlib Date: Thu, 11 Jun 2020 13:41:15 -0400 In-Reply-To: References: <20200611093106.GC15174@raven.inka.de> Organization: Red Hat User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.5 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: newlib@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Newlib mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2020 17:41:22 -0000 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 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.