From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] udev-164: don't hardcode path to pidof
Date: Thu, 08 Mar 2012 22:19:45 +0100 [thread overview]
Message-ID: <4F592271.1040407@opendreambox.org> (raw)
In-Reply-To: <1331241161-13878-1-git-send-email-obi@opendreambox.org>
On 08.03.2012 22:12, Andreas Oberritter wrote:
> * pidof lives in /bin, search it in $PATH.
> * Assume pidof's presence.
> * Remove -e shell option, because pidof may return nonzero.
I just noticed that v1 was already merged, so I'll send an incremental
patch in a minute.
Regards,
Andreas
prev parent reply other threads:[~2012-03-08 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 21:12 [PATCH v2] udev-164: don't hardcode path to pidof Andreas Oberritter
2012-03-08 21:19 ` Andreas Oberritter [this message]
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=4F592271.1040407@opendreambox.org \
--to=obi@opendreambox.org \
--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