From: Arnaldo Carvalho de Melo <acme@infradead.org> To: Sam Ravnborg <sam@ravnborg.org> Cc: Borislav Petkov <bp@amd64.org>, Ingo Molnar <mingo@kernel.org>, Michal Marek <mmarek@suse.cz>, LKML <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v5 5/5] tools: Connect to the kernel build system Date: Thu, 12 Apr 2012 16:31:50 -0300 [thread overview] Message-ID: <20120412193150.GR16257@infradead.org> (raw) In-Reply-To: <20120412191611.GB30472@merkur.ravnborg.org> Em Thu, Apr 12, 2012 at 09:16:11PM +0200, Sam Ravnborg escreveu: > On Thu, Apr 12, 2012 at 03:33:51PM -0300, Arnaldo Carvalho de Melo wrote: > > Em Thu, Apr 12, 2012 at 05:57:34PM +0200, Sam Ravnborg escreveu: > > > Who-ever came up with the names "QUIET_SUBDIR" must have had a bad day... > > Came from the git sources, where it still lives on: > > [acme@sandy git]$ git show b7774343 > > commit b777434383bd2f365be6896d8c89be6c1b62a135 > > Author: Alex Riesen <raa.lkml@gmail.com> > > Date: Wed Mar 7 00:44:49 2007 +0100 > > Support of "make -s": do not output anything of the build itself > > Signed-off-by: Junio C Hamano <junkio@cox.net> > Part of the git build infrastructure has not impressed me - others parts are good. > But then it is more than a year since I actually looked at it. > > And no - I have no time left to actually do anything about it. Neither me, similar impressions, for the Makefiles, I really want us to move to what is used by our landlord, the kernel :-) I also can see doing a 'make tools/menuconfig' to select what we want to build in a particular perf build, for instance, I received requests for building just 'perf record' to use it in embedded systems, collect your events, push it to another machine, where one would use a full featured perf build. Or one without perl, if one hates that thing :-) - Arnaldo
next prev parent reply other threads:[~2012-04-12 19:31 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-11 16:36 [PATCH v5 0/5] tools: Add a toplevel Makefile Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 1/5] tools: Add Makefile.include Borislav Petkov 2012-04-13 18:14 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 2/5] tools: Cleanup EXTRA_WARNINGS Borislav Petkov 2012-04-13 18:15 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 3/5] tools: Add a toplevel Makefile Borislav Petkov 2012-04-13 18:16 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 4/5] tools: Add a help target Borislav Petkov 2012-04-13 18:17 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 5/5] tools: Connect to the kernel build system Borislav Petkov 2012-04-11 18:04 ` Arnaldo Carvalho de Melo 2012-04-11 18:08 ` Arnaldo Carvalho de Melo 2012-04-11 18:19 ` David Ahern 2012-04-11 19:45 ` Borislav Petkov 2012-04-11 19:52 ` Arnaldo Carvalho de Melo 2012-04-12 15:22 ` Borislav Petkov 2012-04-12 15:57 ` Sam Ravnborg 2012-04-12 18:33 ` Arnaldo Carvalho de Melo 2012-04-12 19:16 ` Sam Ravnborg 2012-04-12 19:31 ` Arnaldo Carvalho de Melo [this message] 2012-04-12 21:17 ` Alex Riesen 2012-04-13 10:45 ` Borislav Petkov 2012-04-11 19:47 ` Borislav Petkov 2012-04-13 18:18 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-14 6:35 ` Alex Riesen
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=20120412193150.GR16257@infradead.org \ --to=acme@infradead.org \ --cc=bp@amd64.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=mmarek@suse.cz \ --cc=sam@ravnborg.org \ --subject='Re: [PATCH v5 5/5] tools: Connect to the kernel build system' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.