From: Yuri Weinstein <yweinste@redhat.com>
To: "Dillaman, Jason" <dillaman@redhat.com>
Cc: Sage Weil <sweil@redhat.com>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: luminous branch is now forked
Date: Tue, 8 Aug 2017 07:59:26 -0700 [thread overview]
Message-ID: <CAMMFjmEJycSdnvAei7EJJWc4QddEDi3eOnEPrkKgyHj24cVbLw@mail.gmail.com> (raw)
In-Reply-To: <CA+aFP1AG6Bf4f++h91GPjcp360+FY5gqXyJ_GEJVbvcXjcF15g@mail.gmail.com>
Yes I will add it to nightlies.
On Tue, Aug 8, 2017 at 5:09 AM, Jason Dillaman <jdillama@redhat.com> wrote:
> Should we start running teuthology nightlies against the luminous
> branch (perhaps swapping out kraken)?
>
> On Mon, Aug 7, 2017 at 12:01 PM, Sage Weil <sweil@redhat.com> wrote:
>> The luminous branch is now fully forked from master. Any fixes merged to
>> master need to be cherry-pick -x'd to luminous.
>>
>> There are only 6 open prs with the luminous tag. I'm going to clear the
>> milestone for these shortly so that the luminous milestone can be used for
>> luminous backport PRs.
>>
>> Thanks!
>> sage
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> --
> Jason
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-08 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 16:01 luminous branch is now forked Sage Weil
2017-08-08 12:09 ` Jason Dillaman
2017-08-08 14:59 ` Yuri Weinstein [this message]
2017-08-08 16:59 ` Yuri Weinstein
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=CAMMFjmEJycSdnvAei7EJJWc4QddEDi3eOnEPrkKgyHj24cVbLw@mail.gmail.com \
--to=yweinste@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=sweil@redhat.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.