From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: phillip.lord@russet.org.uk (Phillip Lord) Newsgroups: gmane.emacs.devel Subject: Re: non-fast-forward pushes to Emacs Git repo "scratch" branches? Date: Mon, 20 Jun 2016 16:21:25 +0100 Message-ID: <871t3revii.fsf@russet.org.uk> References: <87fusc0w33.fsf@lifelogs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1466436708 19409 80.91.229.3 (20 Jun 2016 15:31:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Jun 2016 15:31:48 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 20 17:31:39 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bF1Al-0006Zq-HW for ged-emacs-devel@m.gmane.org; Mon, 20 Jun 2016 17:31:35 +0200 Original-Received: from localhost ([::1]:44381 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bF1Ak-0001TQ-K1 for ged-emacs-devel@m.gmane.org; Mon, 20 Jun 2016 11:31:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42450) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bF112-0007N8-GE for emacs-devel@gnu.org; Mon, 20 Jun 2016 11:21:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bF10y-0006kW-Rh for emacs-devel@gnu.org; Mon, 20 Jun 2016 11:21:31 -0400 Original-Received: from cloud103.planethippo.com ([31.216.48.48]:36727) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bF10y-0006kM-DP for emacs-devel@gnu.org; Mon, 20 Jun 2016 11:21:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=russet.org.uk; s=default; h=Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From; bh=5ZZvXWasE8j9y5kHeJ5rYhXfz4igqXj8+pAH0d9FSZs=; b=IuCQjNznaJB6LuFa1TQBxqWK8i lO/LtzyQIEY0VrUm/TX9FiPkhh3nkFnmwqJwzjy6Sngmim9x1NlNFOJp8iFrFNE5gSA9C6BD8tsCK WDpwiWb2WbyWPpKzKB8AOByiSIxVe8jVxn6sSyn/2zaVYis2KrKH+5nU+0U9L9l3MTduUEoS5AnKT P4dB/OmQgX9XzHko8slyHtWVvVv4ddxqO9wCIfbBI2Nk1hp9PDTf5kxH+NhsOCO6kDAs2O7ciHPnQ jrEGKt/JWqq+bAPSStXVYD/8WwYiiP7BWxxs+K8xoO7lL3BhKoRKb07I47Ayyke/M7H7XL1rLjagD /3QsYWJw==; Original-Received: from janus-nat-128-240-225-60.ncl.ac.uk ([128.240.225.60]:32272 helo=russet.org.uk) by cloud103.planethippo.com with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.86_1) (envelope-from ) id 1bF10x-003L85-1A; Mon, 20 Jun 2016 16:21:27 +0100 In-Reply-To: (Stefan Monnier's message of "Fri, 17 Jun 2016 18:25:13 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.95 (gnu/linux) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cloud103.planethippo.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - russet.org.uk X-Get-Message-Sender-Via: cloud103.planethippo.com: authenticated_id: phillip.lord@russet.org.uk X-Authenticated-Sender: cloud103.planethippo.com: phillip.lord@russet.org.uk X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 31.216.48.48 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:204594 Archived-At: Stefan Monnier writes: >> Can the Emacs Git repo allow non-fast-forward pushes to "scratch/*" >> branches? > > No, because the non-fast-forward constraint is applied globally. > But you can delete a branch and then push a new branch under the same > name, with the same end result. It is possible to enforce this on a per branch basis. Just applying it on master and anything starting with "emacs" (for release branches) would do the trick. It would also be possible to prevent, for example, accidental deletions of emacs-25, or master as well as enforce the "don't check into emacs-25 without asking" rule. All good things for newer developers. Phil