All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Cutler <ncutler@suse.cz>
To: "Robin H. Johnson" <robbat2@gentoo.org>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Untested PRs merged to jewel before 10.2.6 release?
Date: Tue, 14 Mar 2017 01:30:35 +0100	[thread overview]
Message-ID: <58362c5b-727a-3cc7-f52e-a01b136617e2@suse.cz> (raw)
In-Reply-To: <robbat2-20170308T014947-232855039Z@orbis-terrarum.net>

>> 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

Thanks, Robin. Opened https://github.com/ceph/ceph/pull/13952 with fix.

Nathan

      reply	other threads:[~2017-03-14  0:30 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
2017-03-14  0:30   ` Nathan Cutler [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=58362c5b-727a-3cc7-f52e-a01b136617e2@suse.cz \
    --to=ncutler@suse.cz \
    --cc=ceph-devel@vger.kernel.org \
    --cc=robbat2@gentoo.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.