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 manual/12751] request to document that mcheck is not thread safe.
Date: Sat, 01 Feb 2014 01:29:00 -0000 [thread overview]
Message-ID: <bug-12751-131-19vwwevnN5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12751-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12751
--- Comment #10 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 9f529d7cfac3afacf602f9f04d8544dbacc33962 (commit)
from 27aaa7911480751feb24d58a20c26890be85f425 (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=9f529d7cfac3afacf602f9f04d8544dbacc33962
commit 9f529d7cfac3afacf602f9f04d8544dbacc33962
Author: Alexandre Oliva <aoliva@redhat.com>
Date: Fri Jan 31 23:28:38 2014 -0200
[BZ #12751]
* manual/memory.texi: Document MTASC-safety properties.
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 5 +
NEWS | 2 +-
manual/memory.texi | 533 ++++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 539 insertions(+), 1 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-01 1:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 17:32 [Bug manual/12751] New: " peeter.joot at gmail dot com
2012-08-30 16:16 ` [Bug manual/12751] " jan.kratochvil at redhat dot com
2013-12-07 5:00 ` cvs-commit at gcc dot gnu.org
2014-01-04 5:41 ` cvs-commit at gcc dot gnu.org
2014-01-09 6:58 ` cvs-commit at gcc dot gnu.org
2014-01-17 1:06 ` cvs-commit at gcc dot gnu.org
2014-01-19 17:10 ` cvs-commit at gcc dot gnu.org
2014-01-23 14:18 ` cvs-commit at gcc dot gnu.org
2014-01-28 4:37 ` cvs-commit at gcc dot gnu.org
2014-01-28 5:54 ` cvs-commit at gcc dot gnu.org
2014-01-30 20:53 ` cvs-commit at gcc dot gnu.org
2014-02-01 1:29 ` cvs-commit at gcc dot gnu.org [this message]
2014-02-01 1:39 ` aoliva at sourceware dot org
2014-06-13 10:57 ` 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-12751-131-19vwwevnN5@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).