public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18641] pwd.h: add __nonnull markings
Date: Wed, 08 Jul 2015 07:22:00 -0000	[thread overview]
Message-ID: <bug-18641-131-SPL1xytc6K@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18641-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18641

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  808696696837b8b8fc858f2e6f8d4e40e26e1308 (commit)
       via  61d95397de01ead73b828c6106a4a832d9681652 (commit)
      from  8b59c73386ddb64331ee03c29925a18dae547733 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=808696696837b8b8fc858f2e6f8d4e40e26e1308

commit 808696696837b8b8fc858f2e6f8d4e40e26e1308
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Sat May 30 14:55:16 2015 -0400

    nscd: drop selinux/flask.h include

    Building nscd w/selinux enabled yields a warning which yields an error:
    In file included from selinux.c:32:0:
    /usr/include/selinux/flask.h:5:2: error:
     #warning "Please remove any #include's of this header in your source
code."

    I've done just that and it builds cleanly with libselinux-2.4.

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=61d95397de01ead73b828c6106a4a832d9681652

commit 61d95397de01ead73b828c6106a4a832d9681652
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Sat May 30 13:33:22 2015 -0400

    pwd.h: add __nonnull markings [BZ #18641]

    Mark all the functions that don't handle NULL pointers as __nonnull.
    POSIX does not require either behavior, so the prototypes should match
    the reality of the codebase.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog      |   15 +++++++++++++++
 NEWS           |    2 +-
 nscd/selinux.c |    1 -
 pwd/pwd.h      |   18 +++++++++++-------
 4 files changed, 27 insertions(+), 9 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  reply	other threads:[~2015-07-08  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08  7:16 [Bug libc/18641] New: " vapier at gentoo dot org
2015-07-08  7:22 ` cvs-commit at gcc dot gnu.org [this message]
2015-07-08  7:22 ` [Bug libc/18641] " vapier at gentoo dot org
2015-07-24 14:44 ` fweimer at redhat dot com
2015-07-28  3:41 ` vapier at gentoo dot org
2015-07-28  3:47 ` cvs-commit at gcc dot gnu.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-18641-131-SPL1xytc6K@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: 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).