All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Still <mikal@stillhq.com>
To: Andries Brouwer <aebr@win.tue.nl>
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>
Subject: Re: [PATCH] docbook: Added support for generating man files
Date: Sat, 19 Jul 2003 12:47:31 +1000	[thread overview]
Message-ID: <Pine.LNX.4.44.0307191237540.1829-100000@diskbox.stillhq.com> (raw)
In-Reply-To: <20030719004833.A3174@pclin040.win.tue.nl>

On Sat, 19 Jul 2003, Andries Brouwer wrote:

> Please put all legalities in comments - behind .\" we do not have to read
> them, but they are there if anyone cares.

Ok. After having done some more poking, I can't see a way of doing this 
with docbook2man -- there doesn't appear to be any way of emitting 
comments. There strike me as two options here: write a script to convert 
SGML to man pages, or perhaps just insert a single sentence into the 
"About this Document" section which explains where to look for copyright 
information.

Any thoughts?

Cheers,
Mikal

-- 

Michael Still (mikal@stillhq.com) | Stage 1: Steal underpants
http://www.stillhq.com            | Stage 2: ????
UTC + 10                          | Stage 3: Profit


  reply	other threads:[~2003-07-19  2:32 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
2003-07-19  2:47         ` Michael Still [this message]
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=Pine.LNX.4.44.0307191237540.1829-100000@diskbox.stillhq.com \
    --to=mikal@stillhq.com \
    --cc=aebr@win.tue.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --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.