From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Gitlab Migration Date: Sat, 28 Aug 2021 17:24:12 +0200 Message-ID: <87zgt1iodf.fsf@gnus.org> References: <87h7fcnmq0.fsf@posteo.net> <83tujbqg4j.fsf@gnu.org> <874kbbosht.fsf@gnus.org> <8335qur9h7.fsf@gnu.org> <831r6er6rz.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38205"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: philipk@posteo.net, danflscr@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca, Eli Zaretskii , sir@cmpwn.com To: Theodor Thornhill Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 28 17:25:04 2021 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 1mK0Ce-0009jY-K8 for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 17:25:04 +0200 Original-Received: from localhost ([::1]:56432 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mK0Cd-0007EL-Jx for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 11:25:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38006) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mK0C5-0006Yh-H6 for emacs-devel@gnu.org; Sat, 28 Aug 2021 11:24:29 -0400 Original-Received: from quimby.gnus.org ([2a01:4f9:2b:f0f::2]:33526) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mK0C0-0002sA-Fl; Sat, 28 Aug 2021 11:24:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Mw+CUxaN5Kyecq9nJUhvlHCZNsZKyJ1AVyGAc/D0JHQ=; b=I/S8OhUXIB2TJ51T73rM0SkoYm nCzGh2zikqZHU+Pd34iwcKo1SSIOQqdhaJLYG21j+VOwOr2dpJSVeS9hhASkm4yv28tCSxCH4Ql69 TDyUwZHUktKcx97dhc6zpaCNO1s64Dj2zupz73ZfCNi7cxsHNQzHCKxQe65NUpVc6lJU=; Original-Received: from [84.212.220.105] (helo=elva) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mK0Bp-0004r5-Ef; Sat, 28 Aug 2021 17:24:17 +0200 In-Reply-To: (Theodor Thornhill's message of "Fri, 27 Aug 2021 23:04:55 +0200") Received-SPF: pass client-ip=2a01:4f9:2b:f0f::2; envelope-from=larsi@gnus.org; helo=quimby.gnus.org X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=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.23 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:273325 Archived-At: Theodor Thornhill writes: > ** Submitting patches by email. > It is possible to send patches using a web interface. It works by using > the `prepare a patchset` button on your own clone. So the process > is usually: > - clone the repo > - pull it locally > - do the work > - push the work > - use the `prepare a patchset` button or `git format-patch` Oh, the "prepare a patchset" button sounds very much like Github/Lab's "pull request" button? Is that accurate? > * Code should be accompanied by documentation > * Formatting code commits I don't quite understand why we have these in the Gitlab requirements list -- they seem pretty orthogonal to everything. > * Closely integrated bugtracker > automated tasks for patch application and status updates exist here Is an issue automatically closed if we push a change containing a magical string like "closes issue #foo" in the commit message? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no