From: Andries Brouwer <aebr@win.tue.nl>
To: Michael Still <mikal@stillhq.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Sam Ravnborg <sam@ravnborg.org>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andries Brouwer <aebr@win.tue.nl>
Subject: Re: [PATCH] docbook: Added support for generating man files
Date: Sat, 19 Jul 2003 00:48:33 +0200 [thread overview]
Message-ID: <20030719004833.A3174@pclin040.win.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0307190828070.1829-100000@diskbox.stillhq.com>; from mikal@stillhq.com on Sat, Jul 19, 2003 at 08:36:27AM +1000
On Sat, Jul 19, 2003 at 08:36:27AM +1000, Michael Still wrote:
> > IS there any chance it could incorporate the GPL by a slightly smaller
> > reference or even a link for the HTML one, it looks great except that
> > 90% of the manual page is a GPL each time 8)
> Well, the only part which comes from this patch is:
> ... Michael Still (mikal\@stillhq.com) ...
> ... This documentation was generated with kernel version $ARGV[2]. ...
> I can shorten this if people would like.
Commenting on the man page (nroff) version:
Please put the mikal\@stillhq.com in a comment.
Please leave the kernel version.
> The GPL bit people have commented on is actually extracted from the front
> matter of the SGML file being converted inside
> <legalnotice></legalnotice>. Therefore, if the SGML kerneldoc output we
> already have includes the GPL, then so does the man page. I have not
> imposed new license conditions on the documentation.
>
> If people are comfortable with dropping the legal notice, or perhaps
> inserting a line saying "refer to file X for the license on this
> documentation", then I'll do that and send a new patch.
Please put all legalities in comments - behind .\" we do not have to read
them, but they are there if anyone cares.
Andries
next prev parent reply other threads:[~2003-07-18 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 20:48 [PATCH] docbook: Added support for generating man files Sam Ravnborg
2003-07-18 21:23 ` Sam Ravnborg
2003-07-18 21:54 ` Alan Cox
2003-07-18 22:36 ` Michael Still
2003-07-18 22:48 ` Andries Brouwer [this message]
2003-07-19 2:47 ` Michael Still
2003-07-19 7:19 ` Andries Brouwer
2003-07-19 7:25 ` Michael Still
2003-07-19 7:40 ` Sam Ravnborg
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=20030719004833.A3174@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikal@stillhq.com \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.