public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <mulix@mulix.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] fix bug 376 - tiny extra echo in Makefile
Date: Thu, 20 Feb 2003 14:49:48 +0200	[thread overview]
Message-ID: <20030220124948.GC17614@actcom.co.il> (raw)

http://bugme.osdl.org/show_bug.cgi?id=376

It's not really a bug, which means this isn't really a fix, but it
does make things more consistent. Please consider for inclusion or let
me know you aren't interested so I can close the bug. Thanks. 

# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.1004  -> 1.1005 
#	            Makefile	1.362   -> 1.363  
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/02/20	mulix@alhambra.mulix.org	1.1005
# don't print the echo command when printing 'Generating build number'
# --------------------------------------------
#
diff -Nru a/Makefile b/Makefile
--- a/Makefile	Thu Feb 20 13:40:59 2003
+++ b/Makefile	Thu Feb 20 13:40:59 2003
@@ -325,7 +325,7 @@
 define rule_vmlinux__
 	set -e
 	$(if $(filter .tmp_kallsyms%,$^),,
-	  echo '  Generating build number'
+	  @echo '  Generating build number'
 	  . $(src)/scripts/mkversion > .tmp_version
 	  mv -f .tmp_version .version
 	  $(Q)$(MAKE) $(build)=init



-- 
Muli Ben-Yehuda
http://www.mulix.org
http://syscalltrack.sf.net


             reply	other threads:[~2003-02-20 12:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 12:49 Muli Ben-Yehuda [this message]
2003-02-20 15:38 ` [PATCH] fix bug 376 - tiny extra echo in Makefile Kai Germaschewski
2003-02-20 15:49   ` Muli Ben-Yehuda
2003-02-20 17:25   ` Sam Ravnborg

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=20030220124948.GC17614@actcom.co.il \
    --to=mulix@mulix.org \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.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