From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [RFE] Migration to gitlab Date: Sun, 12 May 2019 08:31:19 +0300 Message-ID: <83y33cb5nc.fsf@gnu.org> References: <1552789070.5272.1@yandex.ru> <87imwhmmt8.fsf@gmail.com> <87y347g1l3.fsf@iotcl.com> <9ac21e82-8e47-f9b5-f88d-23c0c56946d1@yandex.ru> <87pnpc1lby.fsf@iotcl.com> <83zhoezdqc.fsf@gnu.org> <87imuivfcr.fsf@iotcl.com> <83k1eyfxls.fsf@gnu.org> <17D21056-10B2-4813-AE90-9B2706936CE9@icloud.com> <83imuifqjc.fsf@gnu.org> <87lfzehrug.fsf@gmail.com> <83k1exec2n.fsf@gnu.org> <8736lkikqf.fsf@gmail.com> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="124033"; mail-complaints-to="usenet@blaine.gmane.org" Cc: toon@iotcl.com, dgutov@yandex.ru, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Alex Gramiak Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 12 07:32:30 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hPh65-000W9U-TD for ged-emacs-devel@m.gmane.org; Sun, 12 May 2019 07:32:30 +0200 Original-Received: from localhost ([127.0.0.1]:38993 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPh64-0004Mb-NZ for ged-emacs-devel@m.gmane.org; Sun, 12 May 2019 01:32:28 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:49455) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPh5L-0004MK-FP for emacs-devel@gnu.org; Sun, 12 May 2019 01:31:44 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52460) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPh5I-00008X-PB; Sun, 12 May 2019 01:31:40 -0400 Original-Received: from [176.228.60.248] (port=4362 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hPh5I-0000nK-9K; Sun, 12 May 2019 01:31:40 -0400 In-reply-to: <8736lkikqf.fsf@gmail.com> (message from Alex Gramiak on Sat, 11 May 2019 18:23:36 -0600) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:236445 Archived-At: > From: Alex Gramiak > Cc: toon@iotcl.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca, dgutov@yandex.ru > Date: Sat, 11 May 2019 18:23:36 -0600 > > I'm not sure about features regarding the discussion itself (though > resolvable discussions[0] might be useful), but the administrative > aspect is (mostly*) more detailed and accessible than debbugs'. [1] is > an overview of issues, [2] is an overview of issue boards, [3] includes > a labeled picture of a typical issue page, and [4] describes the > crosslinking between issues/MRs. Thanks, that was useful reading. > P.S. Another feature that would be nice is protected branches[7], which > I believe would allow for, e.g., release branches to be closed off for > commits (which was discussed recently), and for scratch branches to be > rebased (while disallowing rebasing for other branches). Does this protect only the GitLab's copy of the upstream repository, or can we also protect branches on Savannah via this mechanism?