public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: msokolov@ivan.Harhan.ORG (Michael Sokolov)
Cc: binutils@sources.redhat.com, crossgcc@sources.redhat.com,
	gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: An article about the Cygnus tree
Date: Mon, 04 Sep 2000 19:19:00 -0000	[thread overview]
Message-ID: <200009050218.WAA22284@mal-ach.watson.ibm.com> (raw)
In-Reply-To: <0009050114.AA27252@ivan.Harhan.ORG>

	I find your "Introduction to the Cygnus Tree" to be riddled with
incorrect statements.  I do not understand why you apparently made no
attempt to investigate the facts before publicly releasing a thoroughly
inaccurate document.

	Cygnus, as a company, never has been the official FSF-appointed
maintainer of *ANY* GNU Project package.  Daily and weekly snapshots of
the various packages (gcc, gas, gdb, and binutils) were available to all
active developers prior to the public CVS repositories; they were not
developed solely by Cygnus or the FSF behind closed doors.  EGCS was not
run by Cygnus and characterizing it as competition with FSF's gcc project
is just one of numerous places where the description is far from
objective.  The hosting of the gcc.gnu.org site by Cygnus/Red Hat is not a
"dirty little secret".

	Whatever ax you have to grind, I would appreciate if you would
take it elsewhere instead of applying your prism to everyone else.  I
personally find your terminology and inferences highly offensive.
Spreading this sort of disinformation does not help the Free Software
Movement or help encourage a unified source tree and CVS repository for
GNU toolchain packages.

	The various maintainers and steering committees are not composed
of public relations experts, so we probably have been less communicative
and less quick to refute incorrect rumours than we should have been.
Filling in the missing information with conspiracies and accepting the
negative rumours is a normal human instinct, but easily resolved with a
little bit of investigation before producing a draft document.  I would
appreciate if you would demonstrate some comprehension and productive
involvement before you start patting yourself on the back for getting
things rolling.

David

  reply	other threads:[~2000-09-04 19:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-04 18:15 Michael Sokolov
2000-09-04 19:19 ` David Edelsohn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-06 17:49 Mike Stump
2000-09-06 17:54 ` Jeffrey A Law
2000-09-06 20:20   ` Alexandre Oliva
2000-09-06 12:45 Michael Sokolov
2000-09-06 13:05 ` David Edelsohn
2000-09-05 10:54 Michael Sokolov
2000-09-05 16:13 ` Russ.Shaw
2000-09-05 10:44 Michael Sokolov
2000-09-05 12:01 ` Joe Buck
2000-09-04 21:19 Michael Sokolov
2000-09-04 21:40 ` Russ.Shaw
2000-09-04 17:32 Michael Sokolov
2000-09-04 18:03 ` David Edelsohn
2000-09-04 18:13 ` Jan Dvorak
2000-09-04 21:06   ` Alexandre Oliva
2000-09-04 21:24 ` Joe Buck
2000-09-04 14:21 Michael Sokolov
2000-09-04 16:54 ` Geoff Keating

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=200009050218.WAA22284@mal-ach.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=binutils@sources.redhat.com \
    --cc=crossgcc@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=msokolov@ivan.Harhan.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).