From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] openssh: upgrade to 7.5p1
Date: Fri, 21 Apr 2017 15:37:48 +0300 [thread overview]
Message-ID: <0fdddc1c-ee0b-a491-67d6-410aed103c02@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYrNYscMvV5JBoSq2yicg0KEhyvH0Ao=UxEasQJUgyToA@mail.gmail.com>
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 reopens? I can do that, if I would
> get a clear indication of when that work should start and finish.
>
>
> FWIW I'm collecting patches in ross/mut for when master re-opens.
> They've been posted to the list so don't need re-posting.
That's great, then I can send some things that have piled up now :)
Alex
prev parent reply other threads:[~2017-04-21 12:38 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
2017-04-18 10:20 ` Burton, Ross
2017-04-21 12:37 ` Alexander Kanavin [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=0fdddc1c-ee0b-a491-67d6-410aed103c02@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.