From: David Edelsohn <dje.gcc@gmail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: GCC Development <gcc@gcc.gnu.org>,
GDB Development <gdb@sourceware.org>,
Binutils Development <binutils@sourceware.org>
Subject: Re: GNU Toolchain on Google+ and Twitter
Date: Tue, 24 Sep 2013 17:35:00 -0000 [thread overview]
Message-ID: <CAGWvnym-iXr52MUZL893eecAfRAN+vnSVDftxB2++7jk=Q1-sw@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1309241552370.31872@digraph.polyomino.org.uk>
On Tue, Sep 24, 2013 at 11:54 AM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Tue, 24 Sep 2013, David Edelsohn wrote:
>
>> I have established Google+ and Twitter pages for the GNU Toolchain
>> (GCC, Binutils, GDB) as additional, un-official communication channels
>
> What about covering glibc there as well?
I will add coverage of GLIBC as well. Assistance with topics to
highlight is appreciated.
Thanks, David
next prev parent reply other threads:[~2013-09-24 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 15:33 David Edelsohn
2013-09-24 15:54 ` Joseph S. Myers
2013-09-24 17:35 ` David Edelsohn [this message]
2013-09-24 17:38 ` Diego Novillo
2013-09-24 17:40 ` Andrew Pinski
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='CAGWvnym-iXr52MUZL893eecAfRAN+vnSVDftxB2++7jk=Q1-sw@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.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