[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47268000.4000808@garzik.org>
Date: Mon, 29 Oct 2007 20:51:12 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
CC: Christoph Lameter <clameter@....com>, linux-kernel@...r.kernel.org,
Randy Dunlap <rdunlap@...otime.net>,
Sam Ravnborg <sam@...nborg.org>,
Jens Axboe <jens.axboe@...cle.com>,
Prasanna S Panchamukhi <prasanna@...ibm.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
"David S. Miller" <davem@...emloft.net>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <pzijlstr@...hat.com>,
Philippe Elie <phil.el@...adoo.fr>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"William L. Irwin" <wli@...omorphy.com>,
Arjan van de Ven <arjan@...radead.org>,
Christoph Lameter <christoph@...eter.com>
Subject: Re: [RFC] Create instrumentation directory (git repository)
Mathieu Desnoyers wrote:
> Putting stuff in instrumentation/ by no way means that it becomes
> optional for a subsystem, but merely that it could either export
> information useful for kernel instrumentation or have some
> infrastructure parts merged with others.
More reason why you should not be moving stuff all around the tree...
Really, file structure is one of the LEAST important issues around --
while moving files around introduces a non-zero amount of pain.
New files -- like that godawful and nearly empty samples/ directory --
sure, fix that up before release. But let's not break diffs of existing
architectures without good reason.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists