public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Galassi <rosalia@lanl.gov>
To: Eric Bischoff <ebisch@cybercable.tm.fr>
Cc: Jochem Huhmann <joh@gmx.net>,
	docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: --parser and --nochunks are available
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <87bt4o4z1l.fsf@portacipria.lanl.gov> (raw)
In-Reply-To: <38BD2E8F.A3A3F14@cybercable.tm.fr>

    Eric> No, but db2man can become part of the docbook-utils ;-)

Definitely: this, together with all other such useful scripts (like
the texinfo ones) should be merged in.

For robustness of the distribution, though, we need to make sure that
there is a tight loop with the maintainers of these packages.

If they have a regular release process, we can latch in to it and use
it for packaging.  If they don't, we can invite them to maintain the
programs in our repository.

  parent reply	other threads:[~2000-12-27  6:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 db* does it serve the purpose madhu
2000-12-27  6:36 ` Eric Bischoff
2000-12-27  6:36 ` Jorge Godoy
2000-12-27  6:36   ` (docbook-tools) " Eric Bischoff
2000-12-27  6:36     ` Jochem Huhmann
2000-12-27  6:36       ` Eric Bischoff
2000-12-27  6:36         ` Jochem Huhmann
2000-12-27  6:36     ` madhu
     [not found]       ` <38BC0BF9.1E8F29B8@cybercable.tm.fr>
2000-12-27  6:36         ` --parser and --nochunks are available madhu
2000-12-27  6:36           ` man page for docbook-utils scripts Eric Bischoff
2000-12-27  6:36           ` --parser and --nochunks are available Jorge Godoy
2000-12-27  6:36             ` Jochem Huhmann
2000-12-27  6:36               ` Eric Bischoff
2000-12-27  6:36                 ` Edward C. Bailey
2000-12-27  6:36                 ` Jorge Godoy
2000-12-27  6:36                 ` Jochem Huhmann
2000-12-27  6:36                 ` Mark Galassi [this message]
2000-12-27  6:36     ` (docbook-tools) Re: db* does it serve the purpose Jorge Godoy
2000-12-27  6:36       ` Jochem Huhmann
2000-12-27  6:36 ` Mark Galassi
2000-12-27  6:36   ` madhu

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=87bt4o4z1l.fsf@portacipria.lanl.gov \
    --to=rosalia@lanl.gov \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=ebisch@cybercable.tm.fr \
    --cc=joh@gmx.net \
    /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).