From: Felipe Contreras <felipe.contreras@gmail.com>
To: Todd Zullinger <tmz@pobox.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
"brian m . carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH] doc: remove GNU troff workaround
Date: Tue, 21 Mar 2023 16:17:55 -0600 [thread overview]
Message-ID: <CAMP44s38Hnhb-FjAYBQtHVRBcW7wDhd6ah3veemGSw+XdeamaA@mail.gmail.com> (raw)
In-Reply-To: <ZBoqpba+z+/lsTZC@pobox.com>
On Tue, Mar 21, 2023 at 4:07 PM Todd Zullinger <tmz@pobox.com> wrote:
>
> Jeff King wrote:
> > I could believe that some people are still stuck on 2016-era versions of
> > dependencies, but yeah, I agree we can be a little more cavalier with
> > documentation. Anyway, I think the right date really is 2010, as above.
>
> I tested this on with CentOS 7 ( docbook-style-xsl-1.78.1).
>
> I didn't notice any bogus curly quotes in the output. So
> even one of the older OS releases we tend to support
> shouldn't be affected by this change.
>
> Happy to see the cruft removed. :)
For the record, you can check that the fix is there by opening any of
the manpages:
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el .ds Aq '
--
Felipe Contreras
prev parent reply other threads:[~2023-03-21 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 19:00 [PATCH] doc: remove GNU troff workaround Felipe Contreras
2023-03-21 17:32 ` Jeff King
2023-03-21 17:47 ` Junio C Hamano
2023-03-21 18:17 ` Jeff King
2023-03-21 18:27 ` Junio C Hamano
2023-03-21 18:34 ` Felipe Contreras
2023-03-21 20:38 ` Junio C Hamano
2023-03-21 22:07 ` Todd Zullinger
2023-03-21 22:17 ` Felipe Contreras [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMP44s38Hnhb-FjAYBQtHVRBcW7wDhd6ah3veemGSw+XdeamaA@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=tmz@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).