From: "Carlos O'Donell" <carlos@redhat.com>
To: Andrew Stubbs <ams@codesourcery.com>,
Roland McGrath <roland@hack.frob.com>,
libc-ports@sourceware.org
Subject: Re: libc-ports mailing list is going away
Date: Fri, 02 May 2014 08:38:00 -0000 [thread overview]
Message-ID: <53635973.4040501@redhat.com> (raw)
In-Reply-To: <536358FC.5080400@codesourcery.com>
On 05/02/2014 04:36 AM, Andrew Stubbs wrote:
> On 01/05/14 18:01, Roland McGrath wrote:
>> Sometime soon, messages sent to libc-ports will start bouncing. The
>> archives at https://sourceware.org/ml/libc-alpha/ will remain accessible
>> for the foreseeable future.
>
> Either I misunderstood, or you really meant here:
>
> https://sourceware.org/ml/libc-ports/
It's a typo-proof day.
c.
next prev parent reply other threads:[~2014-05-02 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 17:01 Roland McGrath
2014-05-02 8:36 ` Andrew Stubbs
2014-05-02 8:38 ` Carlos O'Donell [this message]
2014-05-02 18:20 ` Roland McGrath
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=53635973.4040501@redhat.com \
--to=carlos@redhat.com \
--cc=ams@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.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).