From: Andi Kleen <andi@firstfloor.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [3/3] KBUILD: Add a "bin" symlink for the scripts directory too
Date: Wed, 7 Jan 2009 22:30:32 +0100 [thread overview]
Message-ID: <20090107213032.GM496@one.firstfloor.org> (raw)
In-Reply-To: <20090107202712.GI4647@uranus.ravnborg.org>
On Wed, Jan 07, 2009 at 09:27:12PM +0100, Sam Ravnborg wrote:
> On Sat, Jan 03, 2009 at 03:21:43AM +0100, Andi Kleen wrote:
> >
> > Several of the scripts in "scripts" are useful to operate on
> > files in a separate objdir. Instead of always manually typing
> > the path to the source dir create a convenient symlink to
> > the source dir's script directory in the objdir too.
> >
> > I named it bin because scripts was already used for the object
> > files of scripts.
>
> So you suggest we in the O=... case should have
> a bin symlink to save you typing "source/sc<tab>
Yes.
>
> That does not justify another symlink in the output
> directory.
Why not? They don't cost anything, do they? And
convenience matters.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2009-01-07 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 2:21 [PATCH] [1/3] KBUILD: Add script to manipulate .config files on the command line Andi Kleen
2009-01-03 2:21 ` [PATCH] [2/3] KBUILD: Add a symlink to the source for separate objdirs Andi Kleen
2009-01-07 20:29 ` Sam Ravnborg
2009-01-03 2:21 ` [PATCH] [3/3] KBUILD: Add a "bin" symlink for the scripts directory too Andi Kleen
2009-01-07 20:27 ` Sam Ravnborg
2009-01-07 21:30 ` Andi Kleen [this message]
2009-01-07 21:36 ` Sam Ravnborg
2009-01-03 10:54 ` [PATCH] [1/3] KBUILD: Add script to manipulate .config files on the command line Arnd Bergmann
2009-01-03 17:12 ` Andi Kleen
2009-01-07 20:18 ` Sam Ravnborg
2009-01-07 21:33 ` Andi Kleen
2009-01-07 22:07 ` 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=20090107213032.GM496@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).