Re: man-pages maintainership (was: Re: [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support)

From: Alejandro Colomar <alx.manpages@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
	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: Tue, 7 Jun 2022 11:37:30 +0200	[thread overview]
Message-ID: <b961003a-0e32-cc6b-9f87-66ae21d37f35@gmail.com> (raw)
In-Reply-To: <7eb14472-d269-ecc6-1ef4-6ea81949efb1@redhat.com>

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

Hi David,

On 6/7/22 09:44, David Hildenbrand wrote:
> Ah, that explains things. The man-page info page [1] was/is still
> pointing at that git tree, that's why I wondered what happened.

Yup.  BTW, that reminds me I need to ask how to update that website. 
Now that everything goes back to normal, I don't need to; but still 
should know how to.

>>> I'm not very concerned about this, since in essence, a fork of the
>>> manual pages is still very well maintained on my server, and free for
>>> anyone interested in reading up-to-date pages.  And since I do this on a
>>> hobby basis (my company doesn't pay me to do this at all), I don't care
>>> at all about not having released in almost a year now.  That's more of a
>>> problem for distros and companies, which need releases.  For
> 
> Heh, including me ;)

Which part of that text includes you?  "interested in reading up-to-date 
pages"?  Or "need releases"?  Or both?  :-)

> 
>>> individuals, I recommend getting a copy of my manual pages' git repo and
>>> `make install`.
> 
> The point I was missing is that there is a fork(). I haven't seen notice
> of that, that's why I asked.
> 
> It might have been helpful to reply with something like "Patch applied
> to my man-pages git fork"., including an URL. But you seem to have
> access to the official man-pages project now, which is good to know.

Yup.  Sorry, I was a bit lazy :)

> 
>>>
>>> I applied recently for a kernel.org account, so maybe the official repo
>>> can be maintained again soon.  Still, I don't expect releasing soon even
>>> if I get access to kernel.org and can update the git repo.  I need to
>>> learn how to do a release properly before I'll release a new version,
>>> and that will take a lot more effort and time from my side than updating
>>> the repo.
>>>
>>> Thanks for your patience!
> 
> Thanks for your hard, voluntary work!

=)

> 
>>
>> BTW, I just released a signed git tag in my repo, to make it a bit more
>> secure to know that you're getting my manual pages, and not some MITM
>> fake stuff.
>>
>> <http://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/tag/?h=man-pages-5.19-rc1>
>>
>> My PGP key is signed by mtk.  Only trust it if it has his signature.
>> I'm attaching it in this email, so that it can be found in the list (I'm
>> having some issue with the keyserver).
> 
> I can spot it on the official git tree [2] as well, essentially via
> alx/main. Nice.

Yes, and soon in master. :)
Still far from a release, however; I need help with that.

Cheers,

Alex

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

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