From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Where in the (info) manual is the license statement supposed to go?
Date: Sun, 11 Dec 2005 17:09:00 -0000 [thread overview]
Message-ID: <20051211170859.GA23733@nevyn.them.org> (raw)
In-Reply-To: <ud5k4ckye.fsf@gnu.org>
On Sun, Dec 11, 2005 at 06:32:41AM +0200, Eli Zaretskii wrote:
> IANAL, but to me, the fact that we have the terms in the file is
> enough. They are not part of the manual itself. In a sense, this is
> analogous to an executable program: you only see the terms if you
> invoke it with a special command-line option.
Or "show copying", in the case of GDB - I thought this was mandated by
the GNU standards (maintain.texi) for interactive programs, but I can't
find it now, so it's likely I was imaging it.
> That said, if you think this is strange, please write to RMS about it.
I may do that. Thanks.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-12-11 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 1:40 Daniel Jacobowitz
2005-12-10 22:16 ` Eli Zaretskii
2005-12-11 3:52 ` Daniel Jacobowitz
2005-12-11 4:32 ` Eli Zaretskii
2005-12-11 17:09 ` Daniel Jacobowitz [this message]
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=20051211170859.GA23733@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.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