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 nptl/15215] Unify pthread_once implementations. Date: Mon, 20 Oct 2014 16:26:00 -0000 [thread overview] Message-ID: <bug-15215-131-xpgtzjlROm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15215-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15215 --- Comment #3 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 63668b7084ac26865136e59fdf17781f9f49bd99 (commit) from 42b7f5d48549b85386a9b28a1a90e66fd81ba273 (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=63668b7084ac26865136e59fdf17781f9f49bd99 commit 63668b7084ac26865136e59fdf17781f9f49bd99 Author: Torvald Riegel <triegel@redhat.com> Date: Fri Oct 11 18:58:04 2013 +0300 pthread_once: Clean up constants. [BZ #15215] This just gives a name to the integer constants being used. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 9 +++++++++ nptl/pthreadP.h | 6 ++++++ nptl/pthread_once.c | 21 ++++++++++++--------- sysdeps/nptl/fork.c | 3 ++- 4 files changed, 29 insertions(+), 10 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-10-20 16:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-28 19:59 [Bug nptl/15215] New: " carlos at redhat dot com 2013-05-24 21:48 ` [Bug nptl/15215] " carlos at redhat dot com 2013-05-24 21:48 ` carlos at redhat dot com 2014-04-11 14:04 ` cvs-commit at gcc dot gnu.org 2014-06-13 18:46 ` fweimer at redhat dot com 2014-10-20 16:26 ` cvs-commit at gcc dot gnu.org [this message] 2014-10-20 19:37 ` triegel at redhat dot com 2014-10-31 21:22 ` 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-15215-131-xpgtzjlROm@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).