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 13:56:31 +0200 Message-ID: References: <83tujbqg4j.fsf@gnu.org> <874kbbosht.fsf@gnus.org> <8335qur9h7.fsf@gnu.org> <831r6er6rz.fsf@gnu.org> <83sfyungux.fsf@gnu.org> <10BD09F0-96B6-4A7C-890C-F738DC50B59D@thornhill.no> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2958"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Alan Third , Eli Zaretskii , Emacs Devel , Lars Ingebrigtsen , Stefan Monnier , danflscr@gmail.com, philipk@posteo.net, sir@cmpwn.com To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 28 13:57:13 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 1mJwxV-0000Sq-AW for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 13:57:13 +0200 Original-Received: from localhost ([::1]:38056 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJwxU-00085Y-9d for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 07:57:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33452) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJwwx-0007QT-Si for emacs-devel@gnu.org; Sat, 28 Aug 2021 07:56:41 -0400 Original-Received: from out2.migadu.com ([2001:41d0:2:aacc::]:35969) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJwwv-0000Ei-2W; Sat, 28 Aug 2021 07:56:39 -0400 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=key1; t=1630151793; 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: in-reply-to:in-reply-to:references:references; bh=02MNSpT4BYsvNwwn2SUWbwOa0uwJBa+BFYbGLqrjj7s=; b=DU6mJ5gGAC2jJ1srvG8wRxcMPkdey+Dlhd8ckocZ/UyVBRZQxY1Toor1AKB6XMeg2AJwU/ sXBwmhVNE+HMg1oMt4blwPwU5BZI+TAeEwk9VcodIPUohfgdz5yL0e/MEuEuylFxUWE5tD Isz/fa3i1wbQKXbiqw7ks3/hhueWhA61Db5kHjDHnUHEe/ZkfVjqsBRStEQCOSHtaaXecH 1LSgMTjfVLI7JkK84kitNT5BvxN3m83HN0J2jqHbprtaAIMu17nKWPrJ4TQhgXeHmo3r/G sL5dh9Pq4RovCoKCoqa9t/g+AL5ssPI0MlN376zBMCD2CDAHs2pRo2pwOFTtxQ== In-Reply-To: X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: theo@thornhill.no Received-SPF: pass client-ip=2001:41d0:2:aacc::; envelope-from=theo@thornhill.no; helo=out2.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:273280 Archived-At: Jean-Christophe Helary writes: >> On Aug 28, 2021, at 20:42, Theodor Thornhill wrote: >> >> Alan Third writes: >> >>> Out of interest, we currently work by attaching patches to emails but >>> I understand the usual "git" way of doing it is by sending the patch >>> directly AS an email. Is that something we'd have to do differently? >> >> Good point. I tried this right now, and it seems like the patch as an >> attachment doesn't work as well... You have to manually view the raw >> patch by expanding the details section then `download raw message` > > Nice to see another sr-ht user here :-) > likewise :) > https://drewdevault.com/2018/07/02/Email-driven-git.html > Though I agree in general with what that blog post states, it isn't really pragmatic enough, imo. If you want to optimize for contributions you have to allow several workflows. Sending a patch as an attachment is, imo a little less daunting than setting up smtp and friends to allow for a typo correction contribution (which is how many people first start contributing). I asked Phil Hagelberg how he handles things in fennel, which is one of sourcehuts flagships if I'm not mistaken: https://icosahedron.website/@technomancy/106830388735139937 -- Theo