From: "Robin H. Johnson" <robbat2@gentoo.org>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Untested PRs merged to jewel before 10.2.6 release?
Date: Wed, 8 Mar 2017 01:50:58 +0000 [thread overview]
Message-ID: <robbat2-20170308T014947-232855039Z@orbis-terrarum.net> (raw)
In-Reply-To: <713de223-60a8-7def-5e59-c6c09b52dc06@suse.cz>
On Tue, Mar 07, 2017 at 10:38:52PM +0100, Nathan Cutler wrote:
> Am I seeing that right? If so, that appears to potentially defeat the
> purpose of the integration testing we do. Maybe I'm overstating the
> danger here -- the commits look innocuous enough -- but it seems to set
> a rather dangerous precedent.
There's a merge error in them too:
qa/suites/rgw/singleton/all/radosgw-admin.yaml
>>>>>>> 8af4c35f95... qa/suites/rgw: Add openstack volume configuration
--
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
next prev parent reply other threads:[~2017-03-08 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 21:38 Untested PRs merged to jewel before 10.2.6 release? Nathan Cutler
2017-03-08 1:50 ` Robin H. Johnson [this message]
2017-03-14 0:30 ` Nathan Cutler
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=robbat2-20170308T014947-232855039Z@orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=ceph-devel@vger.kernel.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.