[Patch 0/1] Remove obsolete compatibility settings for NonStop

[Patch 0/1] Remove obsolete compatibility settings for NonStop

[randall.s.becker]

From: "Randall S. Becker" <rsbecker@nexbridge.com>

Since the original port, capabilities have been added to the
platform that no longer require compatibility emulation.

Randall S. Becker (1):
  config.mak.uname: remove old NonStop platform supported settings.

 config.mak.uname | 4 ----
 1 file changed, 4 deletions(-)

-- 
2.29.2

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

[randall.s.becker]

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.

Signed-off-by: Randall S. Becker <rsbecker@nexbridge.com>
---
 config.mak.uname | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/config.mak.uname b/config.mak.uname
index 5b30a9154a..198ab1e58f 100644
--- a/config.mak.uname
+++ b/config.mak.uname
@@ -574,10 +574,6 @@ ifeq ($(uname_S),NONSTOP_KERNEL)
 	NO_MMAP = YesPlease
 	NO_POLL = YesPlease
 	NO_INTPTR_T = UnfortunatelyYes
-	# Bug report 10-120822-4477 submitted to HP NonStop development.
-	MKDIR_WO_TRAILING_SLASH = YesPlease
-	# RFE 10-120912-4693 submitted to HP NonStop development.
-	NO_SETITIMER = UnfortunatelyYes
 	SANE_TOOL_PATH = /usr/coreutils/bin:/usr/local/bin
 	SHELL_PATH = /usr/coreutils/bin/bash
 endif
-- 
2.29.2

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

[Junio C Hamano]

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.

Will queue.  Thanks.

>
> Signed-off-by: Randall S. Becker <rsbecker@nexbridge.com>
> ---
>  config.mak.uname | 4 ----
>  1 file changed, 4 deletions(-)
>
> diff --git a/config.mak.uname b/config.mak.uname
> index 5b30a9154a..198ab1e58f 100644
> --- a/config.mak.uname
> +++ b/config.mak.uname
> @@ -574,10 +574,6 @@ ifeq ($(uname_S),NONSTOP_KERNEL)
>  	NO_MMAP = YesPlease
>  	NO_POLL = YesPlease
>  	NO_INTPTR_T = UnfortunatelyYes
> -	# Bug report 10-120822-4477 submitted to HP NonStop development.
> -	MKDIR_WO_TRAILING_SLASH = YesPlease
> -	# RFE 10-120912-4693 submitted to HP NonStop development.
> -	NO_SETITIMER = UnfortunatelyYes
>  	SANE_TOOL_PATH = /usr/coreutils/bin:/usr/local/bin
>  	SHELL_PATH = /usr/coreutils/bin/bash
>  endif

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

[Randall S. Becker]

On December 16, 2020 6:27 PM, Junio C Hamano wrote:
> 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