public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nscd/13696] Add a --disable-nscd option to configure for disabling nscd implementation in glibc functions
Date: Wed, 07 Mar 2012 13:25:00 -0000 [thread overview]
Message-ID: <bug-13696-131-pLgIvpGB68@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13696-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13696
--- Comment #3 from Mike Frysinger <vapier at gentoo dot org> 2012-03-07 13:24:54 UTC ---
could you possibly keep the crap out of your comments ? this anti-google
sentiment really has no business here.
but on to the facts:
- the feature in question is *already* in the source (this patch doesn't add
the USE_NSCD define)
- this patch only makes control of the -DUSE_NSCD flag into a configure option
- there should be no ABI change
the amount of additional "overhead" here is trivial. i'd also contend the
assertion that google would be the only consumer of this. plenty of embedded
devices could care less about having a daemon like nscd running.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-03-07 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 23:24 [Bug nscd/13696] New: " benchan at chromium dot org
2012-02-16 17:40 ` [Bug nscd/13696] " ppluzhnikov at google dot com
2012-02-17 23:37 ` vapier at gentoo dot org
2012-03-07 9:18 ` drepper.fsp at gmail dot com
2012-03-07 13:25 ` vapier at gentoo dot org [this message]
2012-08-22 20:42 ` roland at gnu dot org
2014-06-26 15:28 ` fweimer at redhat dot com
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=bug-13696-131-pLgIvpGB68@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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).