From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: fupan.li@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] oe-core: Fix base-files wrong softlink of /var/run and /var/lock
Date: Thu, 18 Feb 2016 08:19:10 +0000 [thread overview]
Message-ID: <1455783550.28376.75.camel@linuxfoundation.org> (raw)
In-Reply-To: <1455761419-21043-1-git-send-email-fupan.li@windriver.com>
On Wed, 2016-02-17 at 18:10 -0800, fupan.li@windriver.com wrote:
> From: fli <fupan.li@windriver.com>
>
> OE-CORE's fs-perms.txt force /var/run to link /run and
> /var/lock to /run/lock, so in order to match with it,
> make base-files /var/run and /var/lock link the absolute
> path too.
You really need to explain what the issue you're solving is here. You
appear to be replacing two relative paths with absolute paths? Why does
this matter?
Cheers,
Richard
next prev parent reply other threads:[~2016-02-18 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 2:10 [PATCH] oe-core: Fix base-files wrong softlink of /var/run and /var/lock fupan.li
2016-02-18 8:19 ` Richard Purdie [this message]
2016-02-18 8:32 ` fupan
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=1455783550.28376.75.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=fupan.li@windriver.com \
--cc=openembedded-core@lists.openembedded.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