linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: David Hildenbrand <david@redhat.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org,
	Axel Rasmussen <axelrasmussen@google.com>,
	Peter Xu <peterx@redhat.com>,
	linux-mm@kvack.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: man-pages maintainership (was: Re: [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support)
Date: Wed, 8 Jun 2022 13:41:38 +0200	[thread overview]
Message-ID: <08d70162-ab3d-faf7-ccf5-3bd55dd810dc@gmail.com> (raw)
In-Reply-To: <9915bba2-ca15-aa4d-eab7-686cd991cd62@redhat.com>


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

Hi David,

On 6/8/22 12:00, David Hildenbrand wrote:
[...]
>>> Heh, including me ;)
>>
>> Which part of that text includes you?  "interested in reading up-to-date
>> pages"?  Or "need releases"?  Or both?  :-)
> 
> A little bit of everything. Obviously, I'm interested in up-to-date man
> pages for Red Hat Linux users :)

:)

[...]
>> Still far from a release, however; I need help with that.
> 
> What kind of help would you be needing?
> 

Okay, so normally, Michael generates a changelog from the git log. 
That's done with a script and then some manual editing.  I've never ever 
written a changelog before, so I'd like to do it as close to what was 
being done before as possible.  Having Michael's script would be nice.

See commit a7846609db2751694c98faa975657ccf990a747a for an example of 
what I need to produce.


I'll also need a script for the timestamps, but I can write that one; it 
should be just a few sh(1) lines.  I'll write that script this week.

Thanks,
Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

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

  reply	other threads:[~2022-06-08 11:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 18:09 [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support Mike Kravetz
2022-05-26 18:21 ` Peter Xu
2022-05-31  9:10 ` David Hildenbrand
2022-06-03 17:02   ` man-pages maintainership (was: Re: [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support) Alejandro Colomar
2022-06-03 17:42     ` Alejandro Colomar
2022-06-07  7:44       ` David Hildenbrand
2022-06-07  9:37         ` Alejandro Colomar
2022-06-08 10:00           ` David Hildenbrand
2022-06-08 11:41             ` Alejandro Colomar [this message]
2022-06-06 19:12 ` [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support 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=08d70162-ab3d-faf7-ccf5-3bd55dd810dc@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=axelrasmussen@google.com \
    --cc=david@redhat.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=mtk.manpages@gmail.com \
    --cc=peterx@redhat.com \
    --cc=torvalds@linux-foundation.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 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 NNTP newsgroup(s).