public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Josh Triplett <josh@joshtriplett.org>,
	linux-man@vger.kernel.org,
	Alejandro Colomar <alx.manpages@gmail.com>
Subject: [PATCH] Remove obsolete admonishment of the GZIP environment variable
Date: Sat, 20 Mar 2021 00:57:22 +0100	[thread overview]
Message-ID: <20210319235717.28264-6-alx.manpages@gmail.com> (raw)

From: Josh Triplett <josh@joshtriplett.org>

gzip deprecated the GZIP environment variable long ago.

Signed-off-by: Josh Triplett <josh@joshtriplett.org>
[ alx: srcfix ]
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
 man7/environ.7 | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/man7/environ.7 b/man7/environ.7
index ee8ca97f6..d618ac749 100644
--- a/man7/environ.7
+++ b/man7/environ.7
@@ -339,16 +339,11 @@ etc.).
 However, in some traditional uses such an environment variable
 gives options for the program instead of a pathname.
 Thus, one has
-.BR MORE ,
-.BR LESS ,
+.B MORE
 and
-.BR GZIP .
+.BR LESS .
 Such usage is considered mistaken, and to be avoided in new
 programs.
-The authors of
-.I gzip
-should consider renaming their option to
-.BR GZIP_OPT .
 .SH SEE ALSO
 .BR bash (1),
 .BR csh (1),
-- 
2.30.1


             reply	other threads:[~2021-03-20  0:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 23:57 Alejandro Colomar [this message]
2021-04-04 19:30 ` [PATCH] Remove obsolete admonishment of the GZIP environment variable Michael Kerrisk (man-pages)
  -- strict thread matches above, loose matches on Subject: below --
2021-03-08 19:07 Josh Triplett
2021-03-10 19:59 ` Alejandro Colomar (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210319235717.28264-6-alx.manpages@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox