public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/1864] bad struct statvfs declaration on Alpha when _FILE_OFFSET_BITS is defined
Date: Wed, 26 Nov 2008 23:28:00 -0000 [thread overview]
Message-ID: <20081126232728.25907.qmail@sourceware.org> (raw)
In-Reply-To: <20051114203814.1864.tsv@solvo.ru>
------- Additional Comments From drepper at redhat dot com 2008-11-26 23:27 -------
Alpha is not in the main tree anymore since we have no maintainer. Somebody has
to step up and volunteer to be the maintainer of the alpha ports tree or nothing
will happen.
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|rth at gcc dot gnu dot org |roland at gnu dot org
Status|ASSIGNED |NEW
Component|libc |ports
http://sourceware.org/bugzilla/show_bug.cgi?id=1864
------- 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:[~2008-11-26 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 20:38 [Bug libc/1864] New: " tsv at solvo dot ru
2005-11-15 15:05 ` [Bug libc/1864] " tsv at solvo dot ru
2005-11-16 20:04 ` drepper at redhat dot com
2005-11-29 9:29 ` stefaan dot deroeck at gmail dot com
2006-03-13 18:51 ` vapier at gentoo dot org
2008-08-12 2:31 ` samuel dot thibault at ens-lyon dot org
2008-08-12 2:32 ` samuel dot thibault at ens-lyon dot org
2008-11-26 23:28 ` drepper at redhat dot com [this message]
[not found] <bug-1864-131@http.sourceware.org/bugzilla/>
2012-02-15 17:46 ` [Bug ports/1864] " jsm28 at gcc dot gnu.org
2012-02-15 18:17 ` rth 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=20081126232728.25907.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).