From: "Maxin B. John" <maxin.john@intel.com>
To: Armin Kuster <akuster808@gmail.com>
Cc: akuster@mvista.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/26] Krogoth-next: stagged changes
Date: Thu, 8 Sep 2016 19:07:50 +0300 [thread overview]
Message-ID: <20160908160749.GB9057@mbabyjoh-desk.ger.corp.intel.com> (raw)
In-Reply-To: <cover.1473349917.git.akuster808@gmail.com>
Hi Armin,
On Thu, Sep 08, 2016 at 08:55:44AM -0700, Armin Kuster wrote:
> The following changes are being considered for krogoth-next.
> If I am missing something, please let me know.
>
Fix for YOCTO #10062 : "[PATCH] useradd_base: avoid unintended expansion for useradd parameters"
is also applicable for krogoth branch.
I have already sent a request for this:
http://lists.openembedded.org/pipermail/openembedded-core/2016-August/125659.html
Is is possible to consider this patch for krogoth ?
<snip>
Best Regards,
Maxin
next prev parent reply other threads:[~2016-09-08 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 15:55 [PATCH 00/26] Krogoth-next: stagged changes Armin Kuster
2016-09-08 16:07 ` Maxin B. John [this message]
2016-09-08 20:00 ` Andre McCurdy
2016-09-12 16:13 ` akuster808
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=20160908160749.GB9057@mbabyjoh-desk.ger.corp.intel.com \
--to=maxin.john@intel.com \
--cc=akuster808@gmail.com \
--cc=akuster@mvista.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