From: Stuart MENEFY <stuart.menefy@st.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] Use relative path when creating include/asm/{mach,cpu}
Date: Mon, 17 Mar 2008 19:51:35 +0000 [thread overview]
Message-ID: <47DECBC7.8070802@st.com> (raw)
In-Reply-To: <47DEC594.6010502@gmail.com>
Franck Bui-Huu wrote:
> From: Franck Bui-Huu <fbuihuu@gmail.com>
>
> Usually relative paths are preferred because they survive directory
> moves, work across networked file systems/chrooted environments.
>
> And in this case, there's no point to use absolute paths.
I've not had a chance to check this, but are you sure this will work
when building with O= (aka KBUILD_OUTPUT) set?
Stuart
next prev parent reply other threads:[~2008-03-17 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 19:25 [PATCH] Use relative path when creating include/asm/{mach,cpu} symlinks Franck Bui-Huu
2008-03-17 19:51 ` Stuart MENEFY [this message]
2008-03-18 3:11 ` Paul Mundt
2008-03-18 7:26 ` [PATCH] Use relative path when creating include/asm/{mach,cpu} Franck Bui-Huu
2008-03-18 7:31 ` Franck Bui-Huu
2008-03-18 19:04 ` Franck Bui-Huu
2008-03-21 3:39 ` [PATCH] Use relative path when creating include/asm/{mach,cpu} symlinks Paul Mundt
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=47DECBC7.8070802@st.com \
--to=stuart.menefy@st.com \
--cc=linux-sh@vger.kernel.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 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.