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 09:16:12 +0000 Message-ID: <0f4ca4f3318373557b6f@heytings.org> References: <87h70vbw2f.fsf@gnus.org> <877d1ru3rd.fsf@posteo.net> <87zgenr812.fsf@gmail.com> <7a1185d7c76d3e55bc78@heytings.org> <7a1185d7c7cd09d9c277@heytings.org> <7a1185d7c7f2d4b8e0ec@heytings.org> <0f4ca4f331dd30be2e0f@heytings.org> <0f4ca4f3313c04ee1b60@heytings.org> <0f4ca4f3313e01c3be2a@heytings.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="3E9zjzq6Yd" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37229"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Monnier , Dmitry Gutov , Visuwesh , Philip Kaludercic , Lars Ingebrigtsen , emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Sep 26 11:18:19 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 1ockFm-0009PT-Th for ged-emacs-devel@m.gmane-mx.org; Mon, 26 Sep 2022 11:18:19 +0200 Original-Received: from localhost ([::1]:44864 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ockFl-0006gF-Cu for ged-emacs-devel@m.gmane-mx.org; Mon, 26 Sep 2022 05:18:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47522) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ockDs-0005rt-DX for emacs-devel@gnu.org; Mon, 26 Sep 2022 05:16:20 -0400 Original-Received: from heytings.org ([95.142.160.155]:57174) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ockDp-0006PN-Oe for emacs-devel@gnu.org; Mon, 26 Sep 2022 05:16:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1664183773; bh=NO02SAtE9CiE/t5C3aeoE4RdkLHAWGh3nhUzYPcqHXs=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=GxTFNnkBGJAxl9FiKevths7rHa6rlGDAQVrIY+S7VzneFdb6Q21LZ7SvcA7056qvK TAggcLB0/KR7hc+RNdb5MhNqb6Pfuv+Jzksz+nNnnOUSGQZDwbAeZrJCbxhLZfxZ5G R2PHxlQr9RWf5EiQJM8HgAAQSiVzbqtVCsfRaBl68ourMK7APUwWIQ3H4ToK0L8IDF C95aqgEZvRZhQZyJ1B8vkGlvug2IxamOr41J4xXqXVh9qyCFnuvxJ1InUZSp/au2qr +mA8IlBqMMLyt9ffTmg243uEX35FAKX6OeQU59rQl5uXFbtED1o4y3TeO2QvMZW28t WfXdMoEhhcwaA== In-Reply-To: Content-ID: <0f4ca4f3317fc78c1b00@heytings.org> 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:296268 Archived-At: --3E9zjzq6Yd Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-ID: <0f4ca4f33143f9d8b12b@heytings.org> >> Just try it yourself. git push origin --delete master, git config=20 >> receive.denyDeleteCurrent ignore, git push origin --delete master. > > So this is a documentation bug. > Or an understanding bug =F0=9F=98=89 All Git repositories have a "current" = branch,=20 unless they are in a "detached HEAD" state. Again, a bare repository has= =20 a current branch: it's the branch that you get when you clone it. And=20 "git branch" works in a bare repository, too: you'll see a star in front=20 of is "current" branch. The documentation could be more explicit indeed,=20 but what would be the meaning of receive.denyDeleteCurrent in a bare=20 repository? --3E9zjzq6Yd--