From: Marc Espie <Marc.Espie@liafa.jussieu.fr>
To: binutils@sourceware.cygnus.com
Subject: newbie question
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990513164936.A18941@liafa1.liafa.jussieu.fr> (raw)
First, I'm not officially subscribed to this list... I hope this is ok,
I have access to the ml archives, which is enough for me, especially as
my mailbox is already cluttered...
As an OpenBSD developper, I will be trying to upgrade our toolchain at
some point during the up-coming months... I know for sure that neither
binutils-2.9.1 nor the latest gas snapshot I have found work out of the
box.
Since some problems we have from our tools are obviously tied to not enough
close collaboration with the binutils developpers, I'm intent on feeding back
all changes to binutils maintainers, so that we stop reinventing the wheel...
Two questions:
- what kind of copyright assignment do I need ? I'm already filed for `gcc'
development, do I need to file for `binutils' and `gdb', or is there some
finer discrimination (e.g., `bfd', `gas', `ld'.... what's a separate `program'
in that context ?)
I don't have any material ready for binutils yet, but I know from past
experience that this paperwork can take some time to process...
- are snapshots still alive ? it's slightly more practical for me to work
on snapshots for various reasons (specifically: because we cover roughly 8
architectures, and it's easier for me to track problems occurring with other
developpers that way)
--
Marc Espie
|anime, sf, juggling, unicycle, acrobatics, comics...
|AmigaOS, OpenBSD, C++, perl, Icon, PostScript...
| `real programmers don't die, they just get out of beta'
next reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Marc Espie [this message]
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Marc Espie
1999-07-01 0:00 ` Andreas Schwab
1999-07-01 0:00 ` joel
1999-07-01 0:00 ` Ian Lance Taylor
2002-05-16 9:14 Newbie Question Jeffrey Stephens
2002-05-16 17:58 ` Alan Modra
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=19990513164936.A18941@liafa1.liafa.jussieu.fr \
--to=marc.espie@liafa.jussieu.fr \
--cc=binutils@sourceware.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).