On 04/18/2017 01:20 PM, Burton, Ross wrote:
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
On 18 April 2017 at 11:18, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> 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
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...
Sorry for my rude.
On 2017年04月17日 14:43, 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
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.
Cheers,
Richard
--
Ping.
On 2017年04月11日 10:01, Dengke Du wrote:
Signed-off-by: Dengke Du
---
.../openssh/{openssh_7.4p1.bb => openssh_7.5p1.bb}| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-connectivity/openssh/{openssh_7.4p1.bb =>
Signed-off-by: Dengke Du
---
.../openssh/{openssh_7.4p1.bb => openssh_7.5p1.bb}| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-connectivity/openssh/{openssh_7.4p1.bb =>
openssh_7.5p1.bb} (97%)
diff --git