DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:to:subject:references
	:content-type; q=dns; s=default; b=j338U3slWr9IJ6M+8JfXjmRqQ0UXD
	JQ8+MwOdM2umnaEWfvFu2lebzcbsuvkhsvf0WDjvstS7mFlENmk549YvrNowetK2
	9UvRy8kxJG2x+9pHopn5Z6adeq72zDp+1hM7Oi4rxtmUKr3h9kuoovVtY3fGhopD
	BqVkTbY7USbWQQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5c7d240c.1c69fb81.fdbe4.f90f@mx.google.com>
Date: Mon, 04 Mar 2019 05:11:40 -0800 (PST)
From: Steven Penny <svnpenn AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin-3 and the Bleeding Edge
References: <152XcDme12976Set DOT 1551701152 AT web13 DOT cms DOT usa DOT net>
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Tryst/2.8.0 (cup.github.io/umber/tryst)

On Mon, 04 Mar 2019 06:05:52, "KARL BOTTS" wrote:
> But now and then I need to upgrade a specific package outside of my full
> cygwin update cycle.  E.g., right now I would like to upgrade just git.
>
> So:  Assume for the moment that the latest git package release on the mirrors,
> has been built against cygwin-3 base.  Am I reasonably safe to assume it will
> still work with cygwin-2.11.2?  Does this generalize to all, or at least most,
> other packages?

that is not the best example as the current Cygwin Git is version
2.17.0 (Apr 2018) and 4 minor versions have dropped since then:

- 2.18.0
- 2.19.0
- 2.20.0
- 2.21.0


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple