From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssh: upgrade to 7.5p1
Date: Tue, 18 Apr 2017 13:18:49 +0300 [thread overview]
Message-ID: <067fa2dd-24ee-60bc-4a27-ddf886d66408@linux.intel.com> (raw)
In-Reply-To: <1492411399.19076.58.camel@linuxfoundation.org>
On 04/17/2017 09:43 AM, Richard Purdie wrote:
> On Mon, 2017-04-17 at 12:37 +0800, Dengke Du wrote:
>> Ping.
>
> We do not take upgrades after feature freeze when we're stabilising
> unless there is a pressing reason to do so. Your commit messages makes
> no mention of any pressing reason.
Yes, but... people keep doing it despite you and me and everyone else
telling them not to. How about someone would stash those updates to a
kind of 'master-next-next' branch, and dump them to the list again when
the merge window reopens? I can do that, if I would get a clear
indication of when that work should start and finish.
Alex
next prev parent reply other threads:[~2017-04-18 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 2:01 [PATCH] openssh: upgrade to 7.5p1 Dengke Du
2017-04-17 4:37 ` Dengke Du
2017-04-17 6:43 ` Richard Purdie
2017-04-17 6:45 ` Dengke Du
2017-04-18 10:18 ` Alexander Kanavin [this message]
2017-04-18 10:20 ` Burton, Ross
2017-04-21 12:37 ` Alexander Kanavin
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=067fa2dd-24ee-60bc-4a27-ddf886d66408@linux.intel.com \
--to=alexander.kanavin@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.