All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3 1/2] tm.3type: describe tm_zone, tm_gmtoff
Date: Wed, 20 Jul 2022 00:09:39 +0200	[thread overview]
Message-ID: <3bd974b4-f2df-7189-de6b-ca1be85a3fd6@gmail.com> (raw)
In-Reply-To: <20220719213653.tljzjqkwkl4ckfrl@tarta.nabijaczleweli.xyz>


[-- Attachment #1.1: Type: text/plain, Size: 2139 bytes --]

Hi!

On 7/19/22 23:36, наб wrote:
>>> +.PP
>>> +.BR timezone (3),
>>> +as a variable, is an XSI extension: some systems provide the V7-compatible
>>> +.\" FreeBSD
>>> +.BR timezone ()
>>
>> I've been thinking about if we should put there a section number.
>> I think we should.  Actually, timezone(3) documents the function in NOTES.
> 
> Disagree: timezone() is /not/ timezone(3).

I understand that timezone() is not _our_ timezone(3).  And that's why I 
still have some doubts.  I thought about using timezone(3BSD), but 
sadly, libbsd doesn't provide the timezone() function.

> 
> Our (and XSI) timezone(3) is
>    extern long timezone;
> whereas the V7-compatible timezone() is
>    extern char *timezone(int zone, int dst);
> cf. https://www.freebsd.org/cgi/man.cgi?query=timezone&apropos=0&sektion=0&manpath=FreeBSD+13.1-RELEASE+and+Ports&arch=default&format=html
> 
> That's why I Xred the first usage (which refers to the variable we
> document) and not the second (which refers to a function we don't).

But we do document BSD's timezone() in our timezone(3) (although that 
documentation could probably be improved):


$ man timezone | sed -n '/NOTES/,/^$/p'
NOTES
        4.3BSD had a function char *timezone(zone, dst) that  re‐
        turned  the  name  of  the  timezone corresponding to its
        first argument (minutes West of UTC).  If the second  ar‐
        gument  was  0, the standard name was used, otherwise the
        daylight saving time version.

Considering also man-pages(7):
        SEE ALSO
               [...]

               Given the distributed, autonomous nature  of  FOSS
               projects  and their documentation, it is sometimes
               necessary—and in many cases desirable—that the SEE
               ALSO section includes references to  manual  pages
               provided by other projects.


I'd say we should .Xr (.MR) it.  Until .MR is widely available, .BR (3) 
is good enough :)

Cheers,

Alex


> 
> Thoughts?
> 
> Best,
> наб

-- 
Alejandro Colomar
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-07-19 22:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  1:56 [PATCH 1/5] tm.3type: tfix наб
2022-07-19  1:56 ` [PATCH 2/5] tm.3type: align ranges наб
2022-07-19 11:44   ` Alejandro Colomar
2022-07-19 14:14     ` наб
2022-07-19 14:25       ` Alejandro Colomar
2022-07-19  1:56 ` [PATCH 3/5] tm.3type: tm_year is year minus 1900, not since наб
2022-07-19 11:47   ` Alejandro Colomar
2022-07-19 11:50   ` Alejandro Colomar
2022-07-19  1:56 ` [PATCH 4/5] tm.3type: describe tm_zone, tm_gmtoff наб
2022-07-19 12:17   ` Alejandro Colomar
2022-07-19 12:19     ` Alejandro Colomar
2022-07-19 15:28     ` наб
2022-07-22  3:33     ` G. Branden Robinson
2022-07-22 10:57       ` Alejandro Colomar (man-pages)
2022-07-22 22:20         ` man(7) DS and DE macros (was: [PATCH 4/5] tm.3type: describe tm_zone, tm_gmtoff) G. Branden Robinson
2022-07-22 23:47           ` Alejandro Colomar
2025-10-29  9:07     ` [PATCH 4/5] tm.3type: describe tm_zone, tm_gmtoff G. Branden Robinson
2025-10-29 10:21       ` Alejandro Colomar
2025-10-29 22:30         ` G. Branden Robinson
2025-10-29 22:53           ` Alejandro Colomar
2022-07-19  1:58 ` [PATCH 5/5] ctime.3: remove struct tm vestigia наб
2022-07-19 12:18   ` Alejandro Colomar
2022-07-19 11:38 ` [PATCH 1/5] tm.3type: tfix Alejandro Colomar
2022-07-19 15:35 ` [PATCH v2 1/4] tm.3type: align ranges наб
2022-07-19 18:38   ` [PATCH v3 1/2] tm.3type: describe tm_zone, tm_gmtoff наб
2022-07-19 20:33     ` Alejandro Colomar
2022-07-19 21:36       ` наб
2022-07-19 22:09         ` Alejandro Colomar [this message]
2022-07-19 22:35     ` [PATCH v4 " наб
2022-07-19 22:36     ` [PATCH v4 2/2] ctime.3: remove struct tm vestigia наб
2022-07-20  8:30       ` Alejandro Colomar
2022-07-19 18:39   ` [PATCH v3 " наб
2022-07-19 15:35 ` [PATCH v2 2/4] tm.3type: widen member alignment to take up to const char * наб
2022-07-19 15:59   ` Alejandro Colomar
2022-07-19 15:35 ` [PATCH v2 3/4] tm.3type: describe tm_zone, tm_gmtoff наб
2022-07-19 17:11   ` Alejandro Colomar
2022-07-19 15:35 ` [PATCH v2 4/4] ctime.3: remove struct tm vestigia наб
2022-07-19 17:12   ` 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=3bd974b4-f2df-7189-de6b-ca1be85a3fd6@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.