From: Alejandro Colomar <alx.manpages@gmail.com>
To: David Hildenbrand <david@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
linux-man@vger.kernel.org, linux-mm@kvack.org
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Peter Xu <peterx@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: man-pages maintainership (was: Re: [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support)
Date: Fri, 3 Jun 2022 19:02:30 +0200 [thread overview]
Message-ID: <fef84382-8fd5-92f6-5625-60852c32ea72@gmail.com> (raw)
In-Reply-To: <4ee30efe-4975-66ef-a05c-c5baa7242e98@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1953 bytes --]
Hi David!
On 5/31/22 11:10, David Hildenbrand wrote:
> BTW, the git repository [1] was last updated 2021-09-02. One of my
> patches [2] was apparently picked up (reply via mail) but doesn't appear
> in that repository.
>
> Is the project currently dead/unmaintained or am I just staring at the
> wrong repository?
>
> [1] https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
> [2] https://lkml.kernel.org/r/20210823120645.8223-1-david@redhat.com
>
Your patch has been applied here:
<http://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/man2/madvise.2?id=9f307c06efc8c40a8aff30cf13ef3a8528be9222>
The project is maintained, but the git repository is unmaintained.
I keep reviewing and applying patches in my personal git repository, but
I don't have access to kernel.org yet, so the official sites are
unmaintained. And of course, that also means no releases since 5.13.
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
individuals, I recommend getting a copy of my manual pages' git repo and
`make install`.
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!
Cheers,
Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-03 17:02 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 ` Alejandro Colomar [this message]
2022-06-03 17:42 ` man-pages maintainership (was: Re: [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support) 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
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=fef84382-8fd5-92f6-5625-60852c32ea72@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).