All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonny Grant <jg@jguk.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: should free() refer to posix_memalign?
Date: Sat, 9 Oct 2021 21:15:00 +0100	[thread overview]
Message-ID: <5be88935-1bde-58a0-e01a-40967c5c3041@jguk.org> (raw)
In-Reply-To: <55349181-0ea8-0977-2d3a-a98688ff82de@gmail.com>



On 09/10/2021 19:39, Alejandro Colomar (man-pages) wrote:
> Hi Jonny,
> 
> On 10/8/21 7:57 PM, Jonny Grant wrote:
>> I noticed this page has a date  2021-03-22     for the 5.13 at the footer.
> 
> At each release (actualy, a couple of commits before the release), we run a script that, for each page, checks if a page has been modified during that release.
> 
> If it hasn't been modified, the page will keep its old page timestamp.
> If it has been modified, it will be updated with a timestamp corresponding to the date of the to-be-released release.
> 
> So that date you're seeing is because malloc.3 hasn't been modified since version 5.11 (which was released on 2021-03-22).
> 
> See below some tree view of the history of man3/malloc.3 including releases to explain the above graphically.

Many thanks for the explanation Alex

With kind regards
Jonny

      reply	other threads:[~2021-10-09 20:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 11:19 should free() refer to posix_memalign? Jonny Grant
2021-10-08 12:30 ` Alejandro Colomar (man-pages)
2021-10-08 13:28   ` Jonny Grant
2021-10-08 14:58     ` Alejandro Colomar (man-pages)
2021-10-08 17:57       ` Jonny Grant
2021-10-09 18:39         ` Alejandro Colomar (man-pages)
2021-10-09 20:15           ` Jonny Grant [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5be88935-1bde-58a0-e01a-40967c5c3041@jguk.org \
    --to=jg@jguk.org \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    /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.