public inbox for gnutools-advocacy@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: lxoliva@fsfla.org
Cc: Richard Biener <richard.guenther@gmail.com>,
	gnutools-advocacy@gcc.gnu.org,
	 "Richard M. Stallman" <rms@gnu.org>,
	"Carlos O'Donell" <carlos@systemhalted.org>,
	iains.gcc@gmail.com
Subject: Re: GNU toolchain web page
Date: Mon, 01 Jan 2018 00:00:00 -0000	[thread overview]
Message-ID: <CAGWvnymLyz7987fEVMP151jtm0P4wn+F9D3cHSZSYegs2-gtvg@mail.gmail.com> (raw)
In-Reply-To: <or7eivmft8.fsf@lxoliva.fsfla.org>

Alex,

Please don't redirect a discussion about advocacy for the GNU
Toolchain and the design of the web page into a discussion about GNU
philosophy.  It's rude.  It's not productive.  And it discourages
other people from joining and helping.  Please stop making the
conversation about you and your priorities.  There are many other
mailing lists and forums to discuss this topic for those who wish to
participate.

Thanks, David

On Sat, Oct 6, 2018 at 8:16 AM Alexandre Oliva <lxoliva@fsfla.org> wrote:
>
> On Oct  6, 2018, Richard Biener <richard.guenther@gmail.com> wrote:
>
> > maybe I am too pragmatic to work on FSF owned software.
>
> Pragmatism can only be compared when there's agreement as to the goals
> and their priorities.
>
> It is never pragmatic to sacrifice the main goal for an accessory one,
> but it may be pragmatic to sacrifice an accessory goal for the main one.
>
> --
> Alexandre Oliva, freedom fighter   https://FSFLA.org/blogs/lxo
> Be the change, be Free!         FSF Latin America board member
> GNU Toolchain Engineer                Free Software Evangelist

  reply	other threads:[~2018-10-06 12:52 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
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                   ` Alexandre Oliva
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00                     ` David Edelsohn [this message]
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               ` Richard Stallman
2018-01-01  0:00           ` Richard Stallman
2018-01-01  0:00       ` Alexandre Oliva

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=CAGWvnymLyz7987fEVMP151jtm0P4wn+F9D3cHSZSYegs2-gtvg@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=carlos@systemhalted.org \
    --cc=gnutools-advocacy@gcc.gnu.org \
    --cc=iains.gcc@gmail.com \
    --cc=lxoliva@fsfla.org \
    --cc=richard.guenther@gmail.com \
    --cc=rms@gnu.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).