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/16967] sa_flags has the wrong type
Date: Tue, 20 May 2014 14:15:00 -0000	[thread overview]
Message-ID: <bug-16967-131-MZPqtcpBXA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16967-131@http.sourceware.org/bugzilla/>

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

--- 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  de9d8f2098caeb19684710a3c0774f4fe38a5e2c (commit)
       via  4c0a1e6392fc9f667dba272dc13d94dc5c54813e (commit)
       via  57cce7060a755300273373d3256d6233d73ca013 (commit)
      from  a60339aaff82beadea6f580e587d64052cb5e3b8 (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=de9d8f2098caeb19684710a3c0774f4fe38a5e2c

commit de9d8f2098caeb19684710a3c0774f4fe38a5e2c
Author: Richard Henderson <rth@twiddle.net>
Date:   Tue May 20 07:15:46 2014 -0700

    alpha: fix sa_flags type (BZ 16967)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=4c0a1e6392fc9f667dba272dc13d94dc5c54813e

commit 4c0a1e6392fc9f667dba272dc13d94dc5c54813e
Author: Richard Henderson <rth@twiddle.net>
Date:   Tue May 20 06:59:52 2014 -0700

    alpha: Remove bits/siginfo.h (BZ 16966)

    Using the default header instead.  This matches the kernel, which also
    uses the generic header.  Fixes the sys/wait.h conform issue, where
    si_band had the wrong type.

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=57cce7060a755300273373d3256d6233d73ca013

commit 57cce7060a755300273373d3256d6233d73ca013
Author: Richard Henderson <rth@twiddle.net>
Date:   Sun May 18 22:09:30 2014 -0700

    alpha: Define ELF_MACHINE_NO_RELA

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

Summary of changes:
 ChangeLog                                      |   11 +
 NEWS                                           |    2 +-
 sysdeps/alpha/dl-machine.h                     |    1 +
 sysdeps/unix/sysv/linux/alpha/bits/sigaction.h |    2 +-
 sysdeps/unix/sysv/linux/alpha/bits/siginfo.h   |  333 ------------------------
 5 files changed, 14 insertions(+), 335 deletions(-)
 delete mode 100644 sysdeps/unix/sysv/linux/alpha/bits/siginfo.h

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


  parent reply	other threads:[~2014-05-20 14:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 14:11 [Bug libc/16967] New: " rth at gcc dot gnu.org
2014-05-20 14:11 ` [Bug libc/16967] " rth at gcc dot gnu.org
2014-05-20 14:15 ` cvs-commit at gcc dot gnu.org [this message]
2014-05-20 14:19 ` rth at gcc dot gnu.org
2014-05-20 14:21 ` rth at gcc dot gnu.org
2014-06-12 19:17 ` 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-16967-131-MZPqtcpBXA@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).