threads / patch / 54840

patchRemove obsolete compatibility settings for NonStop

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

## tl;dr

4 messages between Dec 16, 2020 and Dec 17, 2020. Diffs are folded; open one to read it.

replies: 3people: 3as markdown or json

randall.s.becker@rogers.com· Dec 16, 2020, 22:07 UTC · lore
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
randall.s.becker@rogers.com· Dec 16, 2020, 22:07 UTC · re: randall.s.becker@rogers.com · lore

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

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(-)
Show changes to config.mak.uname +0 −4
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
Junio C Hamano· Dec 16, 2020, 23:26 UTC · re: randall.s.becker@rogers.com · lore

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

randall.s.becker@rogers.com writes:
Show 5 quoted lines
> 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.
Show 21 quoted lines
>
> 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
Randall S. Becker· Dec 17, 2020, 12:14 UTC · re: Junio C Hamano · lore

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

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

← back to recent threads