From: Michael Meissner <meissner@the-meissners.org>
To: cgen@sources.redhat.com
Subject: I have returned to the land of free software
Date: Wed, 30 Apr 2003 02:33:00 -0000 [thread overview]
Message-ID: <20030430023313.GA8873@tiktok.the-meissners.org> (raw)
After some periods of unemployment and working for a non-free software company,
I find myself beginning a binutils/GCC/GDB port once again.
I had some problems posting earlier, so I'm trying to debug my sendmail scripts
to make sure I can post to the list.
Could somebody from the FSF send me the current forms that I and my employer
will need to be able to sign in order to be able to contribute future changes
back to the GCC community? I expect I will want to be able to contribute
changes to all of the subdirectories in the compiler suite (I will send this
message to the other major lists too):
bfd
binutils
boehm-gc
cgen
config
contrib
etc
fastjar
gas
gcc
gdb
gprof
include
intl
ld
libf2c
libffi
libgloss
libiberty
libjava
libobjc
libstdc++-v3
maintainer-scripts
mmalloc
newlib
opcodes
readline
sim
texinfo
utils
zlib
--
Michael Meissner
email: gnu@the-meissners.org
http://www.the-meissners.org
reply other threads:[~2003-04-30 2:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030430023313.GA8873@tiktok.the-meissners.org \
--to=meissner@the-meissners.org \
--cc=cgen@sources.redhat.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).