From: Mike Crowe <mac@mcrowe.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 0/2] Use ALTERNATIVES to manage 'nologin'
Date: Mon, 9 Nov 2015 16:36:45 +0000 [thread overview]
Message-ID: <20151109163645.GA6647@mcrowe.com> (raw)
In-Reply-To: <cover.1416554582.git.Qi.Chen@windriver.com>
On Friday 21 November 2014 at 15:27:45 +0800, Chen Qi wrote:
> The following changes since commit 4a888b2ab61662c7f749b5d1e64af92ed613d8eb:
>
> gtk+: drop part of patch adding useless file (2014-11-20 14:08:57 +0000)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib ChenQi/nologin-alternatives
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=ChenQi/nologin-alternatives
>
> Chen Qi (2):
> util-linux: use ALTERNATIVE mechanism to manage 'nologin'
> shadow: use ALTERNATIVE to manage 'nologin'
>
> meta/recipes-core/util-linux/util-linux.inc | 3 ++-
> meta/recipes-extended/shadow/shadow.inc | 7 ++++++-
> 2 files changed, 8 insertions(+), 2 deletions(-)
These patches never seem to make it into master as far as I can see. I
couldn't find any posted objections.
They now require some minor tweaks to apply but appear to work correctly
for me and solve my -dbg package conflicts.
Is there any chance of them being applied?
Thanks.
Mike.
prev parent reply other threads:[~2015-11-09 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 7:27 [PATCH V2 0/2] Use ALTERNATIVES to manage 'nologin' Chen Qi
2014-11-21 7:27 ` [PATCH V2 1/2] util-linux: use ALTERNATIVE mechanism " Chen Qi
2014-11-21 7:27 ` [PATCH V2 2/2] shadow: use ALTERNATIVE " Chen Qi
2015-11-09 16:36 ` Mike Crowe [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=20151109163645.GA6647@mcrowe.com \
--to=mac@mcrowe.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