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 ./ChangeLog ./Makefile ./printconf.s ... Date: Fri, 01 Mar 2002 02:31:00 -0000 [thread overview] Message-ID: <20020301103137.26062.qmail@sources.redhat.com> (raw) CVSROOT: /cvs/rhl Module name: printconf Changes by: twaugh@sources.redhat.com 2002-03-01 02:31:37 Modified files: . : ChangeLog Makefile printconf.spec Added files: usermode : printconf-tui.console printconf-tui.pam redhat-config-printer-tui.console redhat-config-printer-tui.pam Log message: 2002-03-01 Tim Waugh <twaugh@redhat.com> * usermode/printconf-tui.pam, usermode/printconf-tui.console, usermode/redhat-config-printer-tui.pam, usermode/redhat/config-printer-tui.console, Makefile: Use userhelper for printconf-tui as well as printconf-gui (bug #60463). * printconf.spec: Ship /usr/bin/printconf-tui.
reply other threads:[~2002-03-01 10:31 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020301103137.26062.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: linkBe 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).