From: "Frank Ch. Eigler" <fche@redhat.com>
To: sid@sources.redhat.com
Subject: configrun-sid change
Date: Mon, 15 Jan 2001 11:18:00 -0000 [thread overview]
Message-ID: <20010115141806.B16557@redhat.com> (raw)
Hi -
I just checked in a tweak to bsp/configrun-sid that stops doing something
unnecessary. With the change, it is now possible to take a pregenerated
configuration file from sid/bsp/pregen, and monitor its configuration
phase with some verbosity, without having to change that file.
In specific, the following now works:
sid -e "set main verbose? 1" -f pregen/FILE.conf -e "set main verbose? 0"
whereas before, FILE.conf by default used to include
"set main verbose? 0" at the top, which neutered the above trick.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6Y0ztVZbdDOm/ZT0RAjVKAJ9ILRkCJwv8UK1SjX7g+0xzbc0RIACfXyQT
rsHypCkEA2DN8BBDIiFdNzQ=
=gfI0
-----END PGP SIGNATURE-----
reply other threads:[~2001-01-15 11:18 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=20010115141806.B16557@redhat.com \
--to=fche@redhat.com \
--cc=sid@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).