From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Forced push to master
Date: Mon, 09 Dec 2013 00:12:02 +0100 [thread overview]
Message-ID: <52A4FCC2.20902@dachary.org> (raw)
In-Reply-To: <52A4F9F7.8010007@dachary.org>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
On 09/12/2013 00:00, Loic Dachary wrote:
> Hi,
>
> I accidentally forced push to ceph master at 11pm CEST 8 december 2013 the following:
>
> https://github.com/ceph/ceph/commit/17e0a7b2942899e3f4307bf3e9c41bcb4304619d
> https://github.com/ceph/ceph/commit/d5e44cf8b233e517d8f7f26cd556ad0ac15714c1
> https://github.com/ceph/ceph/commit/71f820503a96cafa9e99cca047c3183c375408a8
> https://github.com/ceph/ceph/commit/eefeb0e0ad54fe0179cbf71335a45ea17c0fa23b
> https://github.com/ceph/ceph/commit/8253ff1e0b3b3a1680293c75f015a5cf5f5e34c6
>
> and may have discarded commits done after:
>
> https://github.com/ceph/ceph/commit/94da2153d1e131205c0e5e32601d0b6a9f6a3cfd
>
> which is a merge dated
>
> Date: Sat Dec 7 20:59:22 2013 -0800
>
> I apologize for the inconvenience and trying to figure out more.
http://gitbuilder.sepia.ceph.com/gitbuilder-quantal-amd64/#origin/master
shows:
BUILDING 17e0a7b loic build log osd/OSDMap: add feature bit for TUNABLES3 (== CRUSH_V2)
(Pending) d5e44cf loic mon/OSDMonitor: allow setting 'firefly' tunables
...3...
Warn 94da215 sage Warnings(1) Merge pull request #869 from ceph/wip-crush
since gitbuilder reacts to every commit to master and that it did not pick anything between 94da215 and the forced push, it is somewhat reassuring that no commit were lost. But I'm trying to find a way to be sure.
>
> Cheers
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-12-08 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 23:00 Forced push to master Loic Dachary
2013-12-08 23:12 ` Loic Dachary [this message]
2013-12-08 23:53 ` Loic Dachary
2013-12-09 17:59 ` Sage Weil
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=52A4FCC2.20902@dachary.org \
--to=loic@dachary.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.