From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: libc-ports@sourceware.org, Michael Hope <michael.hope@linaro.org>,
Jon Masters <jcm@redhat.com>
Subject: Re: glibc git trunk builds of ARM GNU/Linux hard-float now use /lib/ld-linux-armhf.so.3.
Date: Tue, 08 May 2012 19:05:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1205081904090.9117@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CADZpyiwt4wyZLb0jMBLtsaFrCqshkNF=w4xzzTeVKRP8PU-EAA@mail.gmail.com>
On Tue, 8 May 2012, Carlos O'Donell wrote:
> Shall we make a NEWS item for this?
NEWS has previously been understood to be about libc, not ports. We could
create a NEWS file for ports, and list in it the numbers of bugs fixed in
ports since 2.15 (which generally have not gone in libc's NEWS file), as
well as new feature information.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2012-05-08 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 18:42 Carlos O'Donell
2012-05-08 19:05 ` Joseph S. Myers [this message]
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=Pine.LNX.4.64.1205081904090.9117@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@systemhalted.org \
--cc=jcm@redhat.com \
--cc=libc-ports@sourceware.org \
--cc=michael.hope@linaro.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).