From: Petr Baudis <pasky-AlSwsSmVLrQ@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
drepper-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH] nscd.8: Correct NOTES section on reloading configuration files
Date: Sat, 6 Dec 2008 11:26:16 +0100 [thread overview]
Message-ID: <20081206102616.GA10491@machine.or.cz> (raw)
In-Reply-To: <cfd18e0f0812051549o3d1d2273j8577bb0c69d71a58-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi,
On Fri, Dec 05, 2008 at 06:49:09PM -0500, Michael Kerrisk wrote:
> On Fri, Dec 5, 2008 at 6:17 PM, Petr Baudis <pasky-AlSwsSmVLrQ@public.gmane.org> wrote:
> > The original notes were obsolete, current nscd watches changes in
> > config files.
>
> Can you provide some supporting information here. Pointers to
> relevant sources, or email threads.
nscd/connections.c, git log nscd/connections.c. ;-)
> I think what I'm really meaning
> is: could you write a nice changelog entry for this patch. Also, my
> reading of the patch is that you are changing the page because glibc
> changed at a certain point. If this is the case, it would be good to
> note in which glibc version the change occurred, and then it would be
> better to rewrite the page to describe old and new behaviors, rather
> than just dropping the text that describes the old behavior. Do you
> see what I mean?
It behaved this way at least since "Sun Oct 18 15:02:11 1998 +0000",
some four months after including the nscd implementation in glibc. But
there does seem to be a short window between glibc-2.1 and glibc-2.1.3
when nscd -i was not available, I don't think it's worth muddling the
point of the page with that, though.
--
Petr "Pasky" Baudis
People who take cold baths never have rheumatism, but they have
cold baths.
--
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
next prev parent reply other threads:[~2008-12-06 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 23:17 [PATCH] nscd.8: Correct NOTES section on reloading configuration files Petr Baudis
[not found] ` <20081205231738.GU10491-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>
2008-12-05 23:49 ` Michael Kerrisk
[not found] ` <cfd18e0f0812051549o3d1d2273j8577bb0c69d71a58-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-06 10:26 ` Petr Baudis [this message]
2008-12-06 17:23 ` Michael Kerrisk
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=20081206102616.GA10491@machine.or.cz \
--to=pasky-alswssmvlrq@public.gmane.org \
--cc=drepper-H+wXaHxf7aLQT0dZR+AlfA@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