From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>
Cc: 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 12:34:51 -0600 [thread overview]
Message-ID: <CAMP44s22GzW6rFEEbNo8Bx3oKhf6occ6+Y8hP+vcp8bid-kqWw@mail.gmail.com> (raw)
In-Reply-To: <20230321181702.GI3119834@coredump.intra.peff.net>
On Tue, Mar 21, 2023 at 12:17 PM Jeff King <peff@peff.net> wrote:
> I suspect they were not using Git back then, and these commits were
> later imported, which may have caused some of our confusion (searching
> for docbook 1.76 shows releases on SourceForge, which implies a non-Git
> VCS).
They were using Subversion:
https://sourceforge.net/p/docbook/code/HEAD/tree/
> The announcement of 1.76.0 in 2010 mentions a fix for the apostrophe
> issue:
>
> https://lists.oasis-open.org/archives/docbook-apps/201009/msg00023.html
The tarball contains the fix:
https://sourceforge.net/projects/docbook/files/docbook-xsl/1.76.0/
So yeah, it was fixed back in 2010.
--
Felipe Contreras
next prev parent reply other threads:[~2023-03-21 18:35 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 [this message]
2023-03-21 20:38 ` Junio C Hamano
2023-03-21 22:07 ` Todd Zullinger
2023-03-21 22:17 ` Felipe Contreras
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=CAMP44s22GzW6rFEEbNo8Bx3oKhf6occ6+Y8hP+vcp8bid-kqWw@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 \
/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).