public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Xavier Leroy <Xavier.Leroy@inria.fr>,
	Arnav Rawat <rawat.arnav@gmail.com>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
	GNU Libc Maintainers <debian-glibc@lists.debian.org>,
	lnx-man <linux-man@vger.kernel.org>,
	glibc <libc-alpha@sourceware.org>,
	Carlos O'Donell <carlos@redhat.com>
Subject: Re: Manual pages from glibc-doc
Date: Tue, 3 Oct 2023 17:10:00 +0200	[thread overview]
Message-ID: <ZRwuyJ47NnNHCspo@debian> (raw)
In-Reply-To: <ZRv9b2Ht-sRok6BH@debian>

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

On Tue, Oct 03, 2023 at 01:39:21PM +0200, Alejandro Colomar wrote:
> Hi Arnav, Xavier,
> 
> On Sun, May 21, 2023 at 07:29:19PM +0200, Xavier Leroy wrote:
> > On Sun, May 21, 2023 at 12:25 PM Alejandro Colomar <alx.manpages@gmail.com>
> > wrote:

[...]

> > > Thanks for the history.  I've investigated a bit after your email.
> > >
> > 
> > Thanks for the historian's work !

I've imported the glibc git history into the Linux man-pages, to keep
that history as untouched as possible.  :)

Please find the import here:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/log/?id=6571dea2f1b71f4bc2ca8c3b9850acccd7226659>

I wonder if there are more pages in other paths within glibc that we
should also import.

I'll push these changes to <kernel.org> to-morrow.

Cheers,
Alex

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

      reply	other threads:[~2023-10-03 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 18:23 Alex Colomar
2023-05-21  9:40 ` Xavier Leroy
2023-05-21 10:24   ` Alejandro Colomar
2023-05-21 10:42     ` Andreas Schwab
2023-05-21 17:29     ` Xavier Leroy
2023-10-03 11:39       ` Alejandro Colomar
2023-10-03 15:10         ` Alejandro Colomar [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=ZRwuyJ47NnNHCspo@debian \
    --to=alx@kernel.org \
    --cc=Xavier.Leroy@inria.fr \
    --cc=alx.manpages@gmail.com \
    --cc=carlos@redhat.com \
    --cc=debian-glibc@lists.debian.org \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=rawat.arnav@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).