From: "Carlos O'Donell" <carlos@systemhalted.org>
To: lxoliva@fsfla.org
Cc: iains.gcc@gmail.com, gnutools-advocacy@gcc.gnu.org
Subject: Re: GNU toolchain web page
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <CAE2sS1jSG=vD2ZeuzjAQaopSNkqf2HHEmbzr_bUfF7om2r9eNA@mail.gmail.com> (raw)
In-Reply-To: <orbm89p8g4.fsf@lxoliva.fsfla.org>
On Thu, Oct 4, 2018 at 8:02 PM Alexandre Oliva <lxoliva@fsfla.org> wrote:
> On Oct 1, 2018, "Carlos O'Donell" <carlos@systemhalted.org> wrote:
> > create a Google doc
>
> Could we please avoid using proprietary tech, that excludes the
> possibility of participation of hardcore Free Software users?
I will try, but in this case the end justifies the means for me. I can
certainly pass around offline copies for review after we markup some
designs for the website.
Cheers,
Carlos.
next prev parent reply other threads:[~2018-10-05 2:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 Iain Sandoe
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Joseph Myers
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Richard Biener
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Carlos O'Donell [this message]
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Stallman
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Biener
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Biener
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Stallman
2018-01-01 0:00 ` Richard Stallman
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='CAE2sS1jSG=vD2ZeuzjAQaopSNkqf2HHEmbzr_bUfF7om2r9eNA@mail.gmail.com' \
--to=carlos@systemhalted.org \
--cc=gnutools-advocacy@gcc.gnu.org \
--cc=iains.gcc@gmail.com \
--cc=lxoliva@fsfla.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).