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: Tue, 28 Jul 2015 03:47:00 -0000	[thread overview]
Message-ID: <bug-18641-131-i2Jjpg30L5@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 #5 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  1eb8bf804937bea53f5e8cfa2f84d256373cdb64 (commit)
      from  3df5cd98371dd9f10b6853efa4d54d359614007d (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=1eb8bf804937bea53f5e8cfa2f84d256373cdb64

commit 1eb8bf804937bea53f5e8cfa2f84d256373cdb64
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Mon Jul 27 23:43:09 2015 -0400

    pwd.h: revert __nonnull markings on putpwent [BZ #18641]

    This function actually checks for NULL arguments and the API has been
    tenatively documented as using EINVAL in that case.  We can debate
    leaving it this way, but it should be done after the pending release.

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

Summary of changes:
 ChangeLog |    5 +++++
 pwd/pwd.h |    2 +-
 2 files changed, 6 insertions(+), 1 deletions(-)

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


      parent reply	other threads:[~2015-07-28  3:47 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 ` [Bug libc/18641] " vapier at gentoo dot org
2015-07-08  7:22 ` cvs-commit at gcc dot gnu.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 [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=bug-18641-131-i2Jjpg30L5@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).