public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox•net>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: Alex Riesen <raa.lkml@gmail•com>,
	"Shawn O. Pearce" <spearce@spearce•org>,
	git@vger•kernel.org
Subject: Re: [PATCH] Make 'make' quieter while building git
Date: Tue, 06 Mar 2007 15:02:56 -0800	[thread overview]
Message-ID: <7vejo2nffj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.63.0703061518250.22628@wbgn013.biozentrum.uni-wuerzburg.de

Johannes Schindelin <Johannes.Schindelin@gmx•de> writes:

> On Tue, 6 Mar 2007, Alex Riesen wrote:
> ...
>> ... I was suggesting to output something like this:
>> 
>> $ make
>> ...
>>     CC builtin-grep.o
>> builtin-grep.c:187: warning: 'external_grep' defined but not used
>> 
>> Notice "builtin-grep.o" (the ".o", not _.c_). IOW, we already
>> see builtin-grep.c when we need it (in the error/warning message),
>> BUT the builtin-grep.o is missing (and is useful for mouse-copy-paste).
>
> Ah! That explains it why I did not understand.

But doesn't "CC foo.o" look just simply WRONG?  We compile foo.c
to produce foo.o.  An alternative that I could slightly more
sympathize with would be something like this:

	CC builtin-grep.c => builtin-grep.o

  reply	other threads:[~2007-03-06 23:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06  6:35 [PATCH] Make 'make' quieter while building git Shawn O. Pearce
2007-03-06  7:03 ` Junio C Hamano
2007-03-06  7:16   ` Shawn O. Pearce
2007-03-06  8:15     ` Junio C Hamano
2007-03-06  8:21       ` Shawn O. Pearce
2007-03-06 10:53     ` Short term release plans Junio C Hamano
2007-03-19 10:53       ` GIT v1.5.1-rc1 Junio C Hamano
2007-03-19 13:21         ` Bill Lear
2007-03-20  1:08           ` Junio C Hamano
2007-03-20  2:55             ` Shawn O. Pearce
2007-03-20  9:37               ` Andy Parkins
2007-03-20 14:42                 ` Shawn O. Pearce
2007-03-20 23:30                   ` Jakub Narebski
2007-03-21  5:06               ` Junio C Hamano
2007-03-21 16:07                 ` Andy Parkins
2007-03-19 14:13         ` Johannes Schindelin
2007-03-20  1:04           ` Junio C Hamano
2007-03-20  1:19             ` Johannes Schindelin
2007-03-06  9:16 ` [PATCH] Make 'make' quieter while building git Alex Riesen
2007-03-06 13:24   ` Johannes Schindelin
2007-03-06 13:37     ` Alex Riesen
2007-03-06 14:19       ` Johannes Schindelin
2007-03-06 23:02         ` Junio C Hamano [this message]
2007-03-06 23:11           ` Alex Riesen
2007-03-06 23:24             ` Shawn O. Pearce

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=7vejo2nffj.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox$(echo .)net \
    --cc=Johannes.Schindelin@gmx$(echo .)de \
    --cc=git@vger$(echo .)kernel.org \
    --cc=raa.lkml@gmail$(echo .)com \
    --cc=spearce@spearce$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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