public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/2167] MIPS build fails due to change to pthreadtype.h
Date: Wed, 18 Jan 2006 08:42:00 -0000 [thread overview]
Message-ID: <20060118084157.13525.qmail@sourceware.org> (raw)
In-Reply-To: <20060117230456.2167.giffordj@linkline.com>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2006-01-18 08:41 -------
Subject: Bug 2167
CVSROOT: /cvs/glibc
Module name: libc
Changes by: aj@sources.redhat.com 2006-01-18 08:41:47
Modified files:
nptl/sysdeps/unix/sysv/linux/mips/bits: pthreadtypes.h
nptl : ChangeLog
Log message:
[BZ #2167]
* sysdeps/unix/sysv/linux/mips/bits/pthreadtypes.h
(pthread_mutex_t): Follow changes for other archs. Based on patch
by Jim Gifford <patches@jg555.com>.
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/nptl/sysdeps/unix/sysv/linux/mips/bits/pthreadtypes.h.diff?cvsroot=glibc&r1=1.1&r2=1.2
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/nptl/ChangeLog.diff?cvsroot=glibc&r1=1.853&r2=1.854
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2167
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2006-01-18 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 23:04 [Bug libc/2167] New: " giffordj at linkline dot com
2006-01-17 23:05 ` [Bug libc/2167] " giffordj at linkline dot com
2006-01-18 8:42 ` cvs-commit at gcc dot gnu dot org [this message]
2006-01-18 8:42 ` aj at suse dot de
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=20060118084157.13525.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).