From: Loic Dachary <loic@dachary.org>
To: Ken Dreyer <kdreyer@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: force pushes disabled for master in ceph.git and ceph-deploy.git
Date: Wed, 10 Dec 2014 23:41:22 +0100 [thread overview]
Message-ID: <5488CC12.5020303@dachary.org> (raw)
In-Reply-To: <5488CA35.1040908@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
On 10/12/2014 23:33, Ken Dreyer wrote:
> On 12/10/2014 03:25 PM, Loic Dachary wrote:
>> On 10/12/2014 23:20, Ken Dreyer wrote:
>>> Thanks to GitHub Support, force-pushes are now disabled for master in
>>> ceph.git and ceph-deploy.git. This should save us from accidentally
>>> deleting history with a bad force-push to the wrong branch. (Not that
>>> any of us were going to do that, of course! :)
>>
>> Thanks ! I did that last year and that makes me appreciate the precaution ;-)
>
> Whoops, so I duplicated your work apparently!
No, I meant I force pushed master inadvertendly last year ;-)
>
> I was thinking that we should do this for the release branches as well?
> So "argonaut", "bobtail", "cuttlefish" "dumpling", "emperor", "firefly",
> "giant"... any other branches?
That would be a good idea.
> And should we open a new support request each time we create a new
> release branch in the future?
Or make it so nobody except a gate has write access, but that's going to take some time.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-12-10 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 22:20 force pushes disabled for master in ceph.git and ceph-deploy.git Ken Dreyer
2014-12-10 22:25 ` Loic Dachary
2014-12-10 22:33 ` Ken Dreyer
2014-12-10 22:41 ` Loic Dachary [this message]
2014-12-10 22:43 ` 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=5488CC12.5020303@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=kdreyer@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.