Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Dave Korn" <dk@artimi.com>
To: "'Ian Lance Taylor'" <ian@wasabisystems.com>
Cc: <gdb@sources.redhat.com>
Subject: RE: GDB is the GNU project's native debugger
Date: Tue, 16 Nov 2004 18:43:00 -0000	[thread overview]
Message-ID: <NUTMEGtjnfZxzd4tHrl000007d6@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <m3lld1slz5.fsf@gossamer.airs.com>

> -----Original Message-----
> From: Ian Lance Taylor 
> Sent: 16 November 2004 18:11

> "Dave Korn" writes:
> 
> >   To my understanding, and correct me if you feel I've 
> misunderstood, a major
> > part of the purpose of the GNU project is to encourage and 
> evangelise the spread
> > of open source, and the strategic method for achieving that 
> goal is to provide
> > free software, in particular a free toolchain, across as 
> wide a range of
> > platforms as possible, 

> For what it's worth, I believe that is to some degree a
> misunderstanding.  The goal of the FSF is a completely free system
> (this goal has been achieved).  This free system is intended to be
> superior both technically and philosophically, and thus encourage
> people to switch to it.
> 
> Running free tools on non-free systems is interesting only to the
> extent that it helps lead to a fully free system.  This happens
> because it encourages a broader range of people to put resources into
> improving the free tools, and thus improving the free system.

> However, running free tools on non-free systems is counterproductive
> to the extent that they make the non-free systems more usable, and
> thus delay the adoption of completely free systems.
> 
> Using the free tools as advertisements of the effectiveness of the GNU
> project is not actually a goal of the FSF, contrary to what you
> suggest.


  Hmm, so do you feel that my first para. would have been more near the truth if
it had said that the encouraging/evangelising of OSS in general was only a
*minor* goal of the gnu project, and that providing free tools on non-free
systems was a tactical method rather than strategic goal?


> All of the above is of course my beliefs based on what I saw as it
> happened, and do not represent any sort of official position by
> anybody.

  You can very certainly <AOL> me on that one!


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


  reply	other threads:[~2004-11-16 18:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 17:14 Andrew Cagney
2004-11-16 17:26 ` Paul Breed
2004-11-16 17:35 ` Kris Warkentin
2004-11-16 20:09   ` Mark Kettenis
2004-11-16 17:50 ` Ian Lance Taylor
2004-11-16 21:48   ` Eli Zaretskii
2004-11-17  1:24   ` Andrew Cagney
2004-11-17  1:53     ` Ian Lance Taylor
2004-11-17 22:59       ` Andrew Cagney
2004-11-19  5:05         ` Ian Lance Taylor
2004-11-19  7:19           ` Kip Macy
2004-11-30 16:26           ` Andrew Cagney
2004-12-07 14:46             ` Ian Lance Taylor
2004-11-16 18:11 ` Dave Korn
2004-11-16 18:33   ` Ian Lance Taylor
2004-11-16 18:43     ` Dave Korn [this message]
2004-11-16 18:47       ` Ian Lance Taylor
2004-11-16 19:59 ` Mark Kettenis
2004-11-17  0:31 ` Steven Johnson
2004-11-16 19:30 Paul Schlie
2004-11-16 19:51 Paul Schlie
2004-11-16 21:11 ` Paul Breed
2004-11-16 23:58   ` Elena Zannoni

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=NUTMEGtjnfZxzd4tHrl000007d6@NUTMEG.CAM.ARTIMI.COM \
    --to=dk@artimi.com \
    --cc=gdb@sources.redhat.com \
    --cc=ian@wasabisystems.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