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 03:52:00 -0000 [thread overview]
Message-ID: <20051211035217.GA15798@nevyn.them.org> (raw)
In-Reply-To: <uk6ecd2dy.fsf@gnu.org>
On Sun, Dec 11, 2005 at 12:16:09AM +0200, Eli Zaretskii wrote:
> > Are these supposed to show up in the Info document?
>
> Not in the parts that the Info reader displays.
OK. I do find that a bit strange, though. It's the license of the
document; we include the full text of the FDL as an appendix, but not
the details of how it applies to the manual you're reading. If I
wanted the licensing terms for an Info manual, Info's where I'd expect
to find them.
I'm fine with my expectations being wrong.
> Why are you asking this? Is there any specific problem with how
> things are currently? This is how every GNU manual handles the GFDL
> mandatory blurbs.
Another Debian developer expressed some confusion over the current
situation, in a bug report.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-12-11 3:52 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 [this message]
2005-12-11 4:32 ` Eli Zaretskii
2005-12-11 17:09 ` Daniel Jacobowitz
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=20051211035217.GA15798@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