LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: use KECHO convenience echo
Date: Fri, 21 Nov 2008 23:01:29 +0100	[thread overview]
Message-ID: <20081121220129.GA18487@uranus.ravnborg.org> (raw)
In-Reply-To: <1225960295-30366-2-git-send-email-vapier@gentoo.org>

On Thu, Nov 06, 2008 at 03:31:35AM -0500, Mike Frysinger wrote:
> Convert a few echos in the build system to new $(KECHO) so we get correct
> output according to build verbosity.
> 
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>

Applied both with a few mods. I will post full kbuild serie
tomorrow.

	Sam


  reply	other threads:[~2008-11-21 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06  8:31 [PATCH] kbuild: introduce KECHO convenience echo Mike Frysinger
2008-11-06  8:31 ` [PATCH] kbuild: use " Mike Frysinger
2008-11-21 22:01   ` Sam Ravnborg [this message]
2008-11-06 20:50 ` [PATCH] kbuild: introduce " Sam Ravnborg
2008-11-06 21:17   ` Mike Frysinger

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=20081121220129.GA18487@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier@gentoo.org \
    /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 NNTP newsgroup(s).