From: Stephen Gregoratto <dev@sgregoratto.me>
To: discuss@mandoc.bsd.lv
Subject: Re: man.cgi and gzip manuals: bug or feature
Date: Sun, 16 Feb 2020 23:55:47 +1100 [thread overview]
Message-ID: <20200216125547.2qzyqppbp7p6rvrm@BlackBox> (raw)
In-Reply-To: <20200216124338.GA34693@www.stare.cz>
On 2020-02-16 13:43, Jan Stary wrote:
> What happens when you name the file appropriately, such as ls.1.gz?
Same thing, raw bytes galore
--
Stephen Gregoratto
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2020-02-16 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 11:59 Stephen Gregoratto
2020-02-16 12:43 ` Jan Stary
2020-02-16 12:55 ` Stephen Gregoratto [this message]
2020-02-16 15:30 ` Ingo Schwarze
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=20200216125547.2qzyqppbp7p6rvrm@BlackBox \
--to=dev@sgregoratto.me \
--cc=discuss@mandoc.bsd.lv \
/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;
as well as URLs for NNTP newsgroup(s).