RE: [Patch 1/1] config.mak.uname: remove old NonStop compatibility settings

From: Randall S. Becker <rsbecker@nexbridge.com>
Date: Dec 17, 2020, 12:14 UTC
Message-ID: <00d301d6d46e$2c7e63e0$857b2ba0$@nexbridge.com>
In-Reply-To: <xmqq1rfp2uyo.fsf@gitster.c.googlers.com>

On December 16, 2020 6:27 PM, Junio C Hamano wrote:

Show 15 quoted lines

> To: randall.s.becker@rogers.com
> Cc: git@vger.kernel.org; Randall S. Becker <rsbecker@nexbridge.com>
> Subject: Re: [Patch 1/1] config.mak.uname: remove old NonStop
> compatibility settings
> 
> randall.s.becker@rogers.com writes:
> 
> > From: "Randall S. Becker" <rsbecker@nexbridge.com>
> >
> > The MKDIR_WO_TRAILING_SLASH and NO_SETITIMER options are no
> longer
> > needed on the NonStop platforms as both are now supported by the
> > oldest supported operating system revision.
> 
> Nice to read "supported by the oldest supported version"; very assuring

that

> it is the right thing to unconditionally remove these settings.

The basic policy is that OS releases (platform calls them RVUs), are supported for 5 years from the date of release. So we are very reluctant to depend on any feature introduced in a more recent RVU. Once the oldest drops off support, we can use newer APIs without concern of a customer hitting a non-supported condition - they can use older versions of git. There are very rare conditions where an incompatibility is introduced, which we try to work around. The now current oldest drops out May 2022. At that point we can prune a few more things. Some customers may stick with older releases (with extra paid support) but my group is not bound to that - independent and volunteers. Of course, if someone wants to pay...

> 
> Will queue.  Thanks.

Thanks, Randall