From: Petr Baudis <pasky-AlSwsSmVLrQ@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Document struct sigevent in sigevent(7)
Date: Tue, 21 Sep 2010 17:31:48 +0200 [thread overview]
Message-ID: <20100921153148.GA8806@machine.or.cz> (raw)
In-Reply-To: <AANLkTin1o4JQ98zmsox6Qg9R5oaPCswieATTd98rCSjY-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi!
On Sun, Sep 19, 2010 at 06:23:03PM +0200, Michael Kerrisk wrote:
> Like I say, when I wrote the timer_create.2 page, I ran into the same
> problems, which is why I partially duplicated content, rather than
> writing a separate page. Of course, this solution doesn't scale well,
> as you highlight. So I think your idea is the right way to go, but it
> needs tweaking. I propose to add the version below. Comments welcome.
Hmm, what you write makes a lot of sense, the new versions looks good
to me!
Thanks for looking into it,
--
Petr "Pasky" Baudis
The true meaning of life is to plant a tree under whose shade
you will never sit.
--
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
prev parent reply other threads:[~2010-09-21 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 11:14 [PATCH] Document struct sigevent in sigevent(7) Petr Baudis
[not found] ` <20090415111442.GN8940-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>
2009-09-20 15:05 ` Petr Baudis
[not found] ` <20090920150500.GO3674-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>
2010-02-24 20:15 ` Petr Baudis
2010-09-19 16:23 ` Michael Kerrisk
[not found] ` <AANLkTin1o4JQ98zmsox6Qg9R5oaPCswieATTd98rCSjY-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-19 16:31 ` Michael Kerrisk
2010-09-21 15:31 ` Petr Baudis [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=20100921153148.GA8806@machine.or.cz \
--to=pasky-alswssmvlrq@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;
as well as URLs for NNTP newsgroup(s).