From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.devel Subject: Re: Amending commits Date: Mon, 26 Sep 2022 07:53:30 +0000 Message-ID: <0f4ca4f331dd30be2e0f@heytings.org> References: <87h70vbw2f.fsf@gnus.org> <877d1ru3rd.fsf@posteo.net> <87zgenr812.fsf@gmail.com> <7a1185d7c76d3e55bc78@heytings.org> <7a1185d7c7cd09d9c277@heytings.org> <7a1185d7c7f2d4b8e0ec@heytings.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14496"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Dmitry Gutov , Visuwesh , Philip Kaludercic , Lars Ingebrigtsen , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Sep 26 10:03:01 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ocj4s-0003UV-I9 for ged-emacs-devel@m.gmane-mx.org; Mon, 26 Sep 2022 10:02:58 +0200 Original-Received: from localhost ([::1]:42344 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ocj4r-0002Vi-A7 for ged-emacs-devel@m.gmane-mx.org; Mon, 26 Sep 2022 04:02:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42634) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ocivm-0003lq-Bx for emacs-devel@gnu.org; Mon, 26 Sep 2022 03:53:42 -0400 Original-Received: from heytings.org ([95.142.160.155]:57014) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ocivk-0001V1-RM for emacs-devel@gnu.org; Mon, 26 Sep 2022 03:53:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1664178810; bh=JZgo/i0KnxozgJ2HZOb/TVj2bY2McQpPc9gMyaXKBEc=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=nBGmZsi7gPz6DsS1duQOko7JSpL04ebfsiwcHJ0yhx+iHxkTcYcnqRRnL0U+MmS5L rndsy5esjj/Rpq1KHWynurSdKccjRiDeClu3kVCmSO8MdNWk1ITGdhDyoNvkjIiOI5 qGTKg3vQoUBhVsQetEfRhPkTwShSJsSB0ufdMHa+i4b2o1iFhY/ge5f/W6fPW9dil5 VKnggvqLiJOdXzg09VKHo0Vu/e5CmMisG2SJUSCfoSrH5BAJixLq2KYKeR0MBkkFnj rw7F2CtoClDq9ydBkSDVhbP8E17DPx7unrlkfDgFVZLWg5SSZbK1bBQso7FL+iknhV EpznvRylfGOQQ== In-Reply-To: Received-SPF: pass client-ip=95.142.160.155; envelope-from=gregory@heytings.org; helo=heytings.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:296259 Archived-At: >> Yes, I said "by default": force pushes are disabled in the default >> settings of Git repositories, unless they have been enabled you cannot >> do that. > > Not sure if this default has changed, but last time I checked the > default was to allow such force pushes (`emacs.git` and `elpa.git` have > explicitly changed this setting to disallow them). You just need to > specify the `--force` option when you push. > These repositories have been created with git init --shared, which automatically sets denyNonFastforwards to true. This has been the default since Git 1.5 in 2007. > > For those repositories like `emacs.git`, `--force` doesn't override the > server's wish, but you can still force push by first deleting the branch > and then pushing the new history. > With branches, yes, but not with master, unless denyDeleteCurrent has been set to warn or ignore. And this is not always possible, even with branches: all deletions can be disallowed by setting receive.denyDeletes to true.