public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: John Marshall <John.W.Marshall@glasgow.ac.uk>,
	"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: Man-pages Git repository
Date: Mon, 21 Mar 2022 17:14:33 -0400	[thread overview]
Message-ID: <YjjquYSCEnlFr0PJ@vapier> (raw)
In-Reply-To: <2d3cff38-ba32-b382-c043-397af12d286b@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

On 16 Mar 2022 18:27, Alejandro Colomar (man-pages) wrote:
> On 3/16/22 14:14, John Marshall wrote:
> > At https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/ it appears that no new commits have been pushed since early September 2021. However here in the linux-man mailing list archives, it appears that changes are continuing to be applied as usual.
> > 
> > I didn't find anything in the mailing list archives discussing this or mentioning a change in repository location. Is there something I'm missing about where to find an up-to-date Git repository for the Linux man pages?
> 
> I keep updating the repository on my own git server,
> <http://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/>.
> That's where patches to the mailing list are being merged since half a
> year ago.
> 
> However, we haven't released any new versions since then.
> There's only the git repository,
> which you can use to get the freshest manual pages,
> or prepare new patches against them.
> 
> We (the maintainers) haven't had much time to prepare a release,
> but the official (kernel.org) repository
> will get updated some time in the future.

please keep the canonical git repo up-to-date.  it's what everyone is using,
and it shouldn't be updated only when releases are pushed.  no one is going
to find your personal server, and if they did, i don't see why anyone would
trust it as the canonical source.
-mike

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

  reply	other threads:[~2022-03-21 21:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 13:14 Man-pages Git repository John Marshall
2022-03-16 17:27 ` Alejandro Colomar (man-pages)
2022-03-21 21:14   ` Mike Frysinger [this message]
2022-03-21 22:55     ` Alejandro Colomar (man-pages)
2022-03-22  9:49       ` Christian Aistleitner
2022-03-22 11:44         ` Alejandro Colomar (man-pages)
2022-06-04  1:26           ` Alejandro Colomar
2022-06-04 11:43             ` Christian Aistleitner

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=YjjquYSCEnlFr0PJ@vapier \
    --to=vapier@gentoo.org \
    --cc=John.W.Marshall@glasgow.ac.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox