From: "Ben Elliston" <bje@au1.ibm.com>
To: binutils@sources.redhat.com
Subject: Re: Use $(SHELL) when running move-if-change
Date: Tue, 21 Dec 2004 05:16:00 -0000 [thread overview]
Message-ID: <20041221051754.GA13842@namadgi> (raw)
In-Reply-To: <20041221032039.GA13097@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 268 bytes --]
> > If we want to get fancy, we could try this patch:
>
> Please. I find the output valuable when I'm trying to see what was
> rebuilt (and the silencing valuable for make -s, too).
Yes, agreed. Okay to commit to src/move-if-change, dear maintainers?
Ben
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-21 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 21:22 Ian Lance Taylor
2004-12-20 23:49 ` Ben Elliston
2004-12-21 2:32 ` Ian Lance Taylor
2004-12-21 3:20 ` Daniel Jacobowitz
2004-12-21 5:16 ` Ben Elliston [this message]
2004-12-21 8:20 ` Nick Clifton
2004-12-21 21:05 ` DJ Delorie
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=20041221051754.GA13842@namadgi \
--to=bje@au1.ibm.com \
--cc=binutils@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).