From: Andi Kleen <andi@firstfloor.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: moving "tools" into the tools/ directory?
Date: Sat, 08 Aug 2009 22:32:33 +0200 [thread overview]
Message-ID: <87bpmqt5b2.fsf@basil.nowhere.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0908081156210.9362@localhost> (Robert P. J. Day's message of "Sat, 8 Aug 2009 11:57:37 -0400 (EDT)")
"Robert P. J. Day" <rpjday@crashcourse.ca> writes:
> is there a standard for moving command-line tools into the top-level
> tools/ directory? as in, Documentation/fs/slabinfo.c? stuff like
> that?
I did some moving of such files from Documentation to tool in a git
tree some time ago, but to make it actually all build sanely --
especially with separate objdirs and/or cross compilation -- would
require major Makefile surgery first.
Current perf is a big pita for separate objdirs and cross compilation
already and it would be probably not a good idea to make it worse for
now.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-08-08 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 15:57 moving "tools" into the tools/ directory? Robert P. J. Day
2009-08-08 20:32 ` Andi Kleen [this message]
2009-08-09 9:08 ` Andi Kleen
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=87bpmqt5b2.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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 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.