From: olea@hispafuentes.com
To: DocBook Mailing List <docbook-tools-discuss@sourceware.cygnus.com>
Cc: Gregory Leblanc <gleblanc@cu-portland.edu>
Subject: Re: (docbook-utils) bug man pages of docbook-utils?
Date: Fri, 12 Jan 2001 14:40:00 -0000 [thread overview]
Message-ID: <3A5F87E0.71538548@hispafuentes.com> (raw)
In-Reply-To: <200101122228.XAA23539@moe.acticiel.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
Gregory Leblanc escribió:
> P.S. Future spec files changes will go to other people who actually
> want them. Who wants the changes to the spec files that are on
> sources.redhat.com?
I like the idea of a set of RPM updated and ready in a unified effort,
if possible.
--
A.Ismael Olea González
tlf 914 575 330
mailto:olea@hispafuentes.com
parent reply other threads:[~2001-01-12 14:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200101122228.XAA23539@moe.acticiel.com>]
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=3A5F87E0.71538548@hispafuentes.com \
--to=olea@hispafuentes.com \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=gleblanc@cu-portland.edu \
/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).