Linux Manual Pages development
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: "libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org"
	<libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org>,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: GSoc 2015 man-pages proposal: a parser for glibc feature test macros
Date: Thu, 19 Feb 2015 09:43:33 -0500	[thread overview]
Message-ID: <54E5F695.1060400@redhat.com> (raw)
In-Reply-To: <CAKgNAkgXgVjNDU=aSVXfdZ5xmo6TZ6qCXhVRNBqte69u6Kas3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 02/19/2015 03:30 AM, Michael Kerrisk (man-pages) wrote:
> Hi Carlos,
> 
> I wonder if I might be able to engage you as a backup mentor for a
> GSoC project that I am proposing here:
> https://www.kernel.org/doc/man-pages/gsoc_2015.html
> 
> The basic idea is to produce a parser for glibc code to tell answer
> the questions: what feature test macros (FTMs) can be defined to
> expose the definition of function foo(). The purpose is then to use
> that information to update FTM information contained in the man pages.
> However, it would of course also be useful information for the glibc
> manual, should the project wish to start documenting such things. (I
> believe this information is little documented in the manual at the
> moment.)
> 
> What do you think of the idea? And would you be willing to be a backup
> mentor? (I expect little effort to be involved on your part, but GSoc
> requires two mentors for a proposal.)
> 
> BTW, if any other glibc maintainer would be willing to act as a backup
> mentor, I'd be happy hear from you.

I would be happy to be a backup mentor.

The idea sounds interesting. I don't know that all combinations of
FTMs are designed to be allowed, and I expect that the result will
always need some human expert cleanup. Therefore it would be good
to have glibc developer review of the results. I'm not suggesting
I should be that reviewer, but the community should review to make
sure it's correct.

Cheers,
Carlos.


--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-02-19 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19  8:30 GSoc 2015 man-pages proposal: a parser for glibc feature test macros Michael Kerrisk (man-pages)
     [not found] ` <CAKgNAkgXgVjNDU=aSVXfdZ5xmo6TZ6qCXhVRNBqte69u6Kas3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-19 14:43   ` Carlos O'Donell [this message]
2015-02-19 18:28     ` Michael Kerrisk (man-pages)
     [not found]       ` <CAKgNAkjmcP=ZKJpPzXAgPXRTAG7pNK9Wr3DKDk+DVf3DJ07B6Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-19 18:42         ` Carlos O'Donell
2015-02-19 19:10           ` Michael Kerrisk (man-pages)
     [not found]             ` <CAKgNAkju9r5_Q8Lw2QgJK2NeUxi222ebSKMfwiO998oK+YQr4A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-19 22:06               ` Carlos O'Donell
     [not found]                 ` <54E65E68.4040003-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-20  6:42                   ` Michael Kerrisk (man-pages)
2015-02-20 16:37                     ` Carlos O'Donell
     [not found]                       ` <54E762CD.7090708-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-20 21:55                         ` Michael Kerrisk (man-pages)
     [not found]                           ` <CAKgNAkgsUHYuLTVOvYj9BRaB_7mea_4BC6Q7ETvHWCk-1Kgfog-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-20 22:13                             ` Carlos O'Donell

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=54E5F695.1060400@redhat.com \
    --to=carlos-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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