From: Loic Dachary <loic@dachary.org>
To: Nathan Cutler <ncutler@suse.cz>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: hammer-backports branch is ready to schedule suites (v0.94.3)
Date: Thu, 16 Jul 2015 01:45:58 +0200 [thread overview]
Message-ID: <55A6F0B6.10707@dachary.org> (raw)
In-Reply-To: <55A6ECAF.4020402@dachary.org>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
Hi Nathan,
Which of https://github.com/ceph/ceph/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+milestone%3Ahammer+ceph.spec.in+in%3Atitle should be built in the gitbuilders first ?
Cheers
On 16/07/2015 01:28, Loic Dachary wrote:
> Hi Abhishek,
>
> The last pull request from the previous integration branch was merged ( https://github.com/ceph/ceph/pull/4891 ).
>
> http://tracker.ceph.com/issues/11990#teuthology-run-commit-0c435d3974c9aa215ea10c6e9eed30ada6dbc390-hammer-backports-July-15
>
> The ceph.spec.in pull request are not included (I made it so all of them have ceph.spec.in in the pull request title) because they conflict and the suite use debian packages.
>
> https://github.com/ceph/ceph/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+milestone%3Ahammer+ceph.spec.in+in%3Atitle
>
> I believe running them one by one through the gitbuilders is the best we can do right now.
>
> Cheers
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-07-15 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 23:28 hammer-backports branch is ready to schedule suites (v0.94.3) Loic Dachary
2015-07-15 23:45 ` Loic Dachary [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=55A6F0B6.10707@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=ncutler@suse.cz \
/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.