From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: Garbled text in zic(8) man page
Date: Tue, 22 Nov 2022 21:41:01 +0100 [thread overview]
Message-ID: <708c2489-4f10-db52-bd49-dba0d3a79238@gmail.com> (raw)
In-Reply-To: <CACb0b4kUmseTdKE-xLRy8KGgtHU011qdYnEWEBfXwsySLJYFWA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1007 bytes --]
Hi Jonathan, Paul,
On 11/22/22 21:39, Jonathan Wakely wrote:
>>> Upstream is https://www.iana.org/time-zones
>>
>> Ahh, I remember last time I wanted to check the source code I desisted because
>> there's no git repository, and I didn't want to be messing with tarballs. But
>> getting the pages from the tarball seems easy, so I'll do that.
>>
>> Paul, do you have a public git (or whatever) repository that I can check out?
>
>
> It looks like there are a few local changes such as replacing
> "degrees" with the degrees symbol, which should probably be preserved
> rather than overwritten by a sync. So it's not just as simple as
> overwriting with the upstream copy. I can try to look into it, but it
> won't be very soon.
Yes, that's why I wanted to get the upstream git repo the other time. Paul, I
have a few fixes for the upstream pages that I'm interested in sending you. A
git repo would be nice :)
Cheers,
Alex
>
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-22 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 12:58 Garbled text in zic(8) man page Jonathan Wakely
2022-11-22 13:00 ` Jonathan Wakely
2022-11-22 13:13 ` Jonathan Wakely
2022-11-22 19:21 ` Alejandro Colomar
2022-11-22 20:31 ` Jonathan Wakely
2022-11-22 20:37 ` Alejandro Colomar
2022-11-22 20:39 ` Jonathan Wakely
2022-11-22 20:41 ` Alejandro Colomar [this message]
2022-11-22 21:00 ` Jakub Wilk
2022-11-22 22:33 ` Alejandro Colomar
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=708c2489-4f10-db52-bd49-dba0d3a79238@gmail.com \
--to=alx.manpages@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=jwakely@redhat.com \
--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