public inbox for rhl-cvs@sourceware.org
help / color / mirror / Atom feed
From: twaugh@sources.redhat.com
To: rhl-cvs@sources.redhat.com
Subject: printconf printconf.spec
Date: Tue, 05 Feb 2002 05:58:00 -0000 [thread overview]
Message-ID: <20020205135758.27180.qmail@sources.redhat.com> (raw)
CVSROOT: /cvs/rhl
Module name: printconf
Changes by: twaugh@sources.redhat.com 2002-02-05 05:57:57
Modified files:
. : printconf.spec
Log message:
* Tue Feb 5 2002 Tim Waugh <twaugh@redhat.com>
- Ship the ChangeLog file.
next reply other threads:[~2002-02-05 13:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 5:58 twaugh [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-13 8:08 twaugh
2002-03-01 9:51 twaugh
2002-02-13 4:49 twaugh
2002-02-11 1:35 twaugh
2002-02-06 9:35 twaugh
2002-01-31 4:51 twaugh
2002-01-29 4:31 twaugh
2002-01-27 10:22 twaugh
2002-01-24 10:06 twaugh
2002-01-24 8:36 twaugh
2002-01-24 8:29 twaugh
2001-12-03 9:37 crutcher
2001-11-08 21:05 crutcher
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=20020205135758.27180.qmail@sources.redhat.com \
--to=twaugh@sources.redhat.com \
--cc=rhl-cvs@sources.redhat.com \
/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).