From: artk@congruent.com (Arthur Kreitman)
To: rms@gnu.ai.mit.edu
Cc: meissner@osf.org, gas2@cygnus.com, bfd@cygnus.com
Subject: Elfdump
Date: Fri, 11 Nov 1994 14:58:00 -0000 [thread overview]
Message-ID: <9411112248.AA18043@Congruent.COM> (raw)
In-Reply-To: <9411112141.AA21468@mole.gnu.ai.mit.edu>
> Date: Fri, 11 Nov 94 16:41:59 -0500
> From: rms@gnu.ai.mit.edu (Richard Stallman)
>
> * fee, provided that the above copyright notice appears in all copies and
> * that both the copyright notice and this permission notice appear in
> * supporting documentation.
>
> Requirements like this about supporting documentation are somewhat
> obnoxious -- as well as legally unenforceable in the US from what I've
> heard -- because they impose a requirement on separate and independent
> works.
Is a binary that comes from your source code a separate work?
next prev parent reply other threads:[~1994-11-11 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-11-11 8:39 Elfdump Michael Meissner
1994-11-11 13:42 ` Elfdump Richard Stallman
1994-11-11 14:58 ` Arthur Kreitman [this message]
1994-11-12 8:41 ` Elfdump Richard Stallman
1994-11-14 6:50 ` Elfdump Michael Meissner
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=9411112248.AA18043@Congruent.COM \
--to=artk@congruent.com \
--cc=bfd@cygnus.com \
--cc=gas2@cygnus.com \
--cc=meissner@osf.org \
--cc=rms@gnu.ai.mit.edu \
/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).