From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Drew DeVault" Newsgroups: gmane.emacs.devel Subject: Re: Gitlab Migration Date: Sat, 28 Aug 2021 20:32:55 +0200 Message-ID: References: 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="31988"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Philip Kaludercic , danflscr@gmail.com, theo@thornhill.no, emacs-devel@gnu.org, monnier@iro.umontreal.ca, Lars Ingebrigtsen , Eli Zaretskii To: =?utf-8?q?Daniel_Mart=C3=ADn?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 28 20:36:16 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 1mK3Bc-00084S-NQ for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 20:36:15 +0200 Original-Received: from localhost ([::1]:49366 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mK3Bb-0003Uo-2e for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 14:36:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33166) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mK3Aq-0002ek-1R for emacs-devel@gnu.org; Sat, 28 Aug 2021 14:35:24 -0400 Original-Received: from out0.migadu.com ([2001:41d0:2:267::]:11421) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mK3Ak-0002ab-E3; Sat, 28 Aug 2021 14:35:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpwn.com; s=key1; t=1630175712; 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; bh=3Z2scKYh/l2nxtopQMEohqpmIHSp93OKKMfW6Dx2Tn0=; b=VVXPPCUSRUCTr5kG7emqAsjRLo8OofWtpkAxlQb5xVeFvtSq73H4hLaX28pQf0Gb8LuCfb +MIfZrn5ngjli8F2OsnSv9Y01aPa9gTHbIm8tWHhIlEhEt4AcMRtz+sawT8GGs4/DkAcqi QjlcK0oEXoqAZeV7aR1HgdV9gDGA13FWWbsiFxkmyttVtZBiLJNfm8e8MnTAsj/3B1vsNK lNVooCDsGAZG0TiKtoShRJqsWwXXI2qAIUyOuPeCutAQxT7iOtKwAg1fxePNINCR2te3KQ 9aITHPW7e28uGEHgOvlMsnJxB6HRHeY/J0CTAzW75MtbfRyMg73AfuYUaJll4A== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-Reply-To: X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: sir@cmpwn.com Received-SPF: pass client-ip=2001:41d0:2:267::; envelope-from=sir@cmpwn.com; helo=out0.migadu.com 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:273347 Archived-At: On Sat Aug 28, 2021 at 8:08 PM CEST, Daniel Mart=C3=ADn wrote: > - It delivers patches in the correct and easily-recognizable format, and > in a more reliable way. (I'm not sure what this means.) Reliability is the main reason for suggesting git send-email :) It does it for you, and does it correctly. > - Makes the job of applying the patches easier and less error-prone. > (Perhaps this just requires learning a new way to work?). Depends, I suppose. > - Allows sending patches whose author is someone other than the email > sender. (I think this is already supported: git config --global > user.email would set the author's email, and git config --global > sendemail.from, or passing the --from=3D
option to git > send-mail, would set the sender's email address.) This just werks by default with git send-email, it automatically adds the author. > But even if patch attachments are not supported by sourcehut, I think > support for image attachments is at least required for some issues. Yeah, we can expand the attachments support for sure. Generally I understand the desire for some projects to have patch attachments as their workflow, but I find that every user who is instructed on git send-email (perhaps by [0]) finds it much better. [0] https://git-send-email.io