Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] initramfs: fix symlink test
Date: Tue, 16 Nov 2010 16:09:52 +0100	[thread overview]
Message-ID: <20101116160952.34c62a20@surf> (raw)
In-Reply-To: <1289919526-2227-1-git-send-email-vapier@gentoo.org>

On Tue, 16 Nov 2010 09:58:46 -0500
Mike Frysinger <vapier@gentoo.org> wrote:

> We want to see if the symlink exists which means -L, not if the target
> of the symlink exists.
> 
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>

Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-11-16 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 14:58 [Buildroot] [PATCH] initramfs: fix symlink test Mike Frysinger
2010-11-16 15:09 ` Thomas Petazzoni [this message]
2010-11-16 15:27 ` Malte Starostik
2010-11-17  6:46 ` [Buildroot] [PATCH v2] initramfs: fix init symlink creation Mike Frysinger
2010-11-17 20:21   ` Peter Korsgaard

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=20101116160952.34c62a20@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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