public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Espie <espie@quatramaran.ens.fr>
To: egcs@egcs.cygnus.com
Subject: Don't wake up the FSF, they need the sleep...
Date: Sat, 30 Jan 1999 11:15:00 -0000	[thread overview]
Message-ID: <199901301914.UAA13240@quatramaran.ens.fr> (raw)
In-Reply-To: <199901301514.KAA13274@blastula.phys.columbia.edu>

In article < 199901301514.KAA13274@blastula.phys.columbia.edu > Zack wrote:

>They've been processed.

>GCC     Marc Espie      France 1967     1999-01-07
>Assigns past and future changes (OpenBSD configuration).
>espie@cvs.openbsd.org
Cool.

>FSF isn't mailing copies back for some reason, but you're in.  I'm
>still waiting for my paperwork to come back, six months later...

This is insane.!! the FSF is the organization which is completely
paranoid about copyright assignments and the GPL. Do they want it
to work ?   They could *at least* try and perform the basic administrative
work correctly... Now, what's going to happen when I find a non-trivial
patch for binutils, or for libiberty ?  Or when I get a patch  from one
of my fellow openbsd developpers which is less than trivial.

I'll have to tell them:
'okay, you have to hunt thru the egcs pages for the copyright assignments,
fill it up, send it in, then wait for one month, and if you haven't heard
from them after that period, start bitching on the egcs mailing-list,
where someone's going to tell you:

Oops, sorry. We processed your papers, but we forgot to tell you about it.'

*How* do you think this reflects on the image of the FSF ?

[include loads of smileys... I'm only half-serious there...]

WARNING: multiple messages have this Message-ID
From: Marc Espie <espie@quatramaran.ens.fr>
To: egcs@egcs.cygnus.com
Subject: Don't wake up the FSF, they need the sleep...
Date: Sun, 31 Jan 1999 23:58:00 -0000	[thread overview]
Message-ID: <199901301914.UAA13240@quatramaran.ens.fr> (raw)
Message-ID: <19990131235800.S6Sm2YR_WLNCMr0F2Yp5FYK2N6-EuGruZHm6dW0jhdc@z> (raw)
In-Reply-To: <199901301514.KAA13274@blastula.phys.columbia.edu>

In article <199901301514.KAA13274@blastula.phys.columbia.edu> Zack wrote:

>They've been processed.

>GCC     Marc Espie      France 1967     1999-01-07
>Assigns past and future changes (OpenBSD configuration).
>espie@cvs.openbsd.org
Cool.

>FSF isn't mailing copies back for some reason, but you're in.  I'm
>still waiting for my paperwork to come back, six months later...

This is insane.!! the FSF is the organization which is completely
paranoid about copyright assignments and the GPL. Do they want it
to work ?   They could *at least* try and perform the basic administrative
work correctly... Now, what's going to happen when I find a non-trivial
patch for binutils, or for libiberty ?  Or when I get a patch  from one
of my fellow openbsd developpers which is less than trivial.

I'll have to tell them:
'okay, you have to hunt thru the egcs pages for the copyright assignments,
fill it up, send it in, then wait for one month, and if you haven't heard
from them after that period, start bitching on the egcs mailing-list,
where someone's going to tell you:

Oops, sorry. We processed your papers, but we forgot to tell you about it.'

*How* do you think this reflects on the image of the FSF ?

[include loads of smileys... I'm only half-serious there...]

  reply	other threads:[~1999-01-30 11:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-29 22:15 Does EGCS Support ARC Catherine Fong
1999-01-29 22:41 ` Warner Losh
1999-01-30  0:01   ` Richard Henderson
1999-01-30  0:40   ` Warner Losh
1999-01-30  5:14     ` Marc Espie
1999-01-30  7:14       ` Zack Weinberg
1999-01-30 11:15         ` Marc Espie [this message]
1999-01-30 11:22           ` Don't wake up the FSF, they need the sleep Jeffrey A Law
1999-01-30 11:29             ` Zack Weinberg
1999-01-31 23:58               ` Zack Weinberg
1999-01-31 23:58             ` Jeffrey A Law
1999-01-31 23:58           ` Marc Espie
1999-01-29 23:55 ` Does EGCS Support ARC Richard Henderson
1999-01-30  4:32 ` Jeffrey A Law

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=199901301914.UAA13240@quatramaran.ens.fr \
    --to=espie@quatramaran.ens.fr \
    --cc=egcs@egcs.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).