public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug linuxthreads/28442] New: Use more unique DYNARRAY_STRUCT name in nss/nss_files/files-hosts.c Date: Mon, 11 Oct 2021 14:54:34 +0000 [thread overview] Message-ID: <bug-28442-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28442 Bug ID: 28442 Summary: Use more unique DYNARRAY_STRUCT name in nss/nss_files/files-hosts.c Product: glibc Version: unspecified Status: NEW Severity: enhancement Priority: P2 Component: linuxthreads Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org CC: drow at false dot org Target Milestone: --- I wonder, is this not a bit too non-specific: ... ./nss/nss_files/files-hosts.c:#define DYNARRAY_STRUCT array ... ? Other entries seem to try harder: ... $ find -type f -name "*.c" | egrep -v "tst|dynarray-skeleton.c" | xargs grep DYNARRAY_STRUCT ./nss/getent.c:#define DYNARRAY_STRUCT gid_list ./nss/nss_action_parse.c:#define DYNARRAY_STRUCT action_list ./nss/nss_files/files-hosts.c:#define DYNARRAY_STRUCT array ./posix/regexec.c:#define DYNARRAY_STRUCT regmatch_list ./posix/register-atfork.c:#define DYNARRAY_STRUCT fork_handler_list ./posix/wordexp.c:#define DYNARRAY_STRUCT strlist ./resolv/res_init.c:#define DYNARRAY_STRUCT nameserver_list ./resolv/res_init.c:#define DYNARRAY_STRUCT search_list ./resolv/res_init.c:#define DYNARRAY_STRUCT sort_list ./resolv/resolv_conf.c:#define DYNARRAY_STRUCT resolv_conf_array ./support/support_descriptors.c:#define DYNARRAY_STRUCT descriptor_list ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-10-11 14:54 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-11 14:54 vries at gcc dot gnu.org [this message] 2021-10-11 15:50 ` [Bug nss/28442] " schwab@linux-m68k.org
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-28442-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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).