From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Theodor Thornhill Newsgroups: gmane.emacs.devel Subject: Re: Gitlab Migration Date: Sat, 28 Aug 2021 10:05:50 +0200 Message-ID: <10BD09F0-96B6-4A7C-890C-F738DC50B59D@thornhill.no> References: <87h7fcnmq0.fsf@posteo.net> <83tujbqg4j.fsf@gnu.org> <874kbbosht.fsf@gnus.org> <8335qur9h7.fsf@gnu.org> <831r6er6rz.fsf@gnu.org> <83sfyungux.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6862"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, larsi@gnus.org, monnier@iro.umontreal.ca, danflscr@gmail.com, philipk@posteo.net, sir@cmpwn.com To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 28 10:06:58 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 1mJtMe-0001X8-VY for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 10:06:57 +0200 Original-Received: from localhost ([::1]:60170 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJtMd-0008NL-Hf for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 04:06:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34810) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJtLi-0007hC-87 for emacs-devel@gnu.org; Sat, 28 Aug 2021 04:05:58 -0400 Original-Received: from out1.migadu.com ([2001:41d0:2:863f::]:29138) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJtLg-0007Gp-Dz; Sat, 28 Aug 2021 04:05:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=key1; t=1630137952; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hUzASm85QpgYgC9yGqkGpJ1nk2IYyms/LGvFmPn8rG8=; b=xxVqK6EyqRQBnFHbtE+5aqvZVqP4VdWucq49nQdcUKYI0l1lvc2kLRfXuLNs01HHMXQbN9 3G1lCsDdpsUEOXbcxBrzMMZekNao/M5X15zqnv0g2irRrS74ObQM3mZu6u8IY4BOEImJR1 I8azeTVdOZwwU6eP8VvjieTgpcQBv7RVY0AYXglOYmNyabzqU0R7aTb8E4u+WFD7NXlyUV oP7xMbPMJaa/Wd6fiMzZVlEKwRTB0BwwS6CU7Ebm6JEs1qPOzA3Xwwl36PPoB8UTg9+z6o kSVEH+WdDT9uFyIzVSESLPbKO9Ts7dLjoF1uCQ4z5kIJzqRumaYr4OC78bmzsw== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-Reply-To: <83sfyungux.fsf@gnu.org> X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: theo@thornhill.no Received-SPF: pass client-ip=2001:41d0:2:863f::; envelope-from=theo@thornhill.no; helo=out1.migadu.com 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_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:273247 Archived-At: On 28 August 2021 09:55:18 CEST, Eli Zaretskii wrote: >> From: Theodor Thornhill >> Cc: emacs-devel@gnu=2Eorg, larsi@gnus=2Eorg, monnier@iro=2Eumontreal=2E= ca, >> danflscr@gmail=2Ecom, philipk@posteo=2Enet, sir@cmpwn=2Ecom >> Date: Fri, 27 Aug 2021 23:04:55 +0200 >>=20 >> ** Submitting patches by email=2E >> It is possible to send patches using a web interface=2E It works by us= ing >> the `prepare a patchset` button on your own clone=2E 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` > >Does it mean simply sending a patch via email is not supported? E=2Eg=2E= , >I could easily create a patch without a separate clone of the >repository, using just the single clone I have already=2E You seem to >describe something much more complicated, which starts with a separate >clone? > No need for a clone=2E Mailing a patch is enough=2E For the web UI thing t= hough I think you need one=2E >> ** Offline review >> An issue (if not already subscribed to all) can be subscribed to your >> own email and be sent to you=2E The whole thing or parts of it can be >> downloaded as an mbox=2E > >Who gets automatically subscribed to an issue? > Collaborators to the repos=2E Otherwise everyone that manually subscribe= =2E You can follow specific issues as well=2E >> ** Reviewing by email >> You can use inline comments [1] > >Do I just respond to an email with the patch, or do I have to use some >special format for the inline comments? > I don't know, sorry=2E I've just seen them=2E >> ** Merge request creation >> Honestly I don't really understand this one=2E=2E=2E > >It's about being able to submit a PR via email=2E > You provide PRs via mail just by sending to the correct list=2E >> * Code should be accompanied by documentation >>=20 >> This seems trivial, and can be done using the CI on patch submission >> running a job, if I understand that point correctly? >>=20 >> * Formatting code commits >> Same as above > >FWIW, I very much doubt these two could be automated, except for very >simple and almost trivial requirements=2E How can a bot decide whether >a change requires documentation changes, and if so, which ones? Even >our formatting of log messages is informal enough to defeat >automation=2E This has to be part of patch review by humans=2E > I won't argue with this=2E >> * Bug reporting >> `report-emacs-bug` can still be used, as well as clicking in the web >> ui=2E This is where I'm not sure about not using email=2E I think you = still >> need to mail the bug, opened by a mailto: > >That's be a disadvantage in my book=2E > Yes it might be=2E >> I hope this helps a little=2E > >It does, thanks a lot! No problem!