On Wed, 10 Dec 2014, 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! > > 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? > > And should we open a new support request each time we create a new > release branch in the future?
The backport branches are occasionally reset; I'd rather not remove that flexibility. They're generally not something people should be developing against so I don't think it's an issue. sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
