From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.bugs Subject: bug#57400: 29.0.50; Support sending patches from VC directly Date: Sat, 27 Aug 2022 08:21:36 +0000 Message-ID: <87v8qecd0v.fsf@posteo.net> References: <84v8qgn1z9.fsf@iki.fi> <87h71zo3p8.fsf@posteo.net> <87sfljmgwz.fsf@posteo.net> <83sflj1dbo.fsf@gnu.org> <87fshjmeje.fsf@posteo.net> <83mtbr1b6l.fsf@gnu.org> <87tu5zky6k.fsf@posteo.net> <83lerb197w.fsf@gnu.org> <87y1vbjfpp.fsf@posteo.net> <83h71z13xc.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="33599"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 57400@debbugs.gnu.org, ane@iki.fi To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Aug 27 10:22:27 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1oRr5D-0008Sx-P0 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 27 Aug 2022 10:22:23 +0200 Original-Received: from localhost ([::1]:49628 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oRr5A-0001Wo-6v for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 27 Aug 2022 04:22:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47532) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRr4s-0001WX-TQ for bug-gnu-emacs@gnu.org; Sat, 27 Aug 2022 04:22:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:37137) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oRr4s-0000Xd-L4 for bug-gnu-emacs@gnu.org; Sat, 27 Aug 2022 04:22:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oRr4s-0003u9-Gl for bug-gnu-emacs@gnu.org; Sat, 27 Aug 2022 04:22:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Philip Kaludercic Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 27 Aug 2022 08:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57400 X-GNU-PR-Package: emacs Original-Received: via spool by 57400-submit@debbugs.gnu.org id=B57400.166158850714978 (code B ref 57400); Sat, 27 Aug 2022 08:22:02 +0000 Original-Received: (at 57400) by debbugs.gnu.org; 27 Aug 2022 08:21:47 +0000 Original-Received: from localhost ([127.0.0.1]:55114 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oRr4d-0003tW-62 for submit@debbugs.gnu.org; Sat, 27 Aug 2022 04:21:47 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]:45001) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oRr4b-0003tC-8B for 57400@debbugs.gnu.org; Sat, 27 Aug 2022 04:21:45 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 8FCDB240026 for <57400@debbugs.gnu.org>; Sat, 27 Aug 2022 10:21:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1661588499; bh=X0pIJ1jvqVDNvEICBGFS+z1IPgEiq6yRRJmNQyzNWW8=; h=From:To:Cc:Subject:Autocrypt:Date:From; b=PeUF7VIoHMK3mcCMtHLN3DE8g7+/N4G8u7Bj1cw+NPiXVU8dmlcZzAduwy56AMs5Z 1/4PmOZ7628Xc/lmP6h/Foo9b+El5AE3ry75SJF2XAF55qffwQp9mR3Vo0E/XRlIFs yc1HV7LwcBBPCjh7nePnlI/LbnqtDjr9789U4InY/YDxhgNgO2mPsSFsVqgipcOFz8 ZKMWoFB5HDGgMF6s+upvY7fbYp8fpflzVP+c49MGxv2PBqfrg4oSLRfGVZZUDIqOtQ 29feAY0DOL/7YRlZN9ds+UCkXHQttZJIIFkU96zK0Y2nDXtN+pK8kNTQGIzOjabJbC 6rNQTCcDjw/ow== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4MF8my3Q3sz6trK; Sat, 27 Aug 2022 10:21:37 +0200 (CEST) In-Reply-To: <83h71z13xc.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 26 Aug 2022 17:21:19 +0300") Autocrypt: addr=philipk@posteo.net; prefer-encrypt=nopreference; keydata= mDMEYHHqUhYJKwYBBAHaRw8BAQdAp3GdmYJ6tm5McweY6dEvIYIiry+Oz9rU4MH6NHWK0Ee0QlBo aWxpcCBLYWx1ZGVyY2ljIChnZW5lcmF0ZWQgYnkgYXV0b2NyeXB0LmVsKSA8cGhpbGlwa0Bwb3N0 ZW8ubmV0PoiQBBMWCAA4FiEEDM2H44ZoPt9Ms0eHtVrAHPRh1FwFAmBx6lICGwMFCwkIBwIGFQoJ CAsCBBYCAwECHgECF4AACgkQtVrAHPRh1FyTkgEAjlbGPxFchvMbxzAES3r8QLuZgCxeAXunM9gh io0ePtUBALVhh9G6wIoZhl0gUCbQpoN/UJHI08Gm1qDob5zDxnIHuDgEYHHqUhIKKwYBBAGXVQEF AQEHQNcRB+MUimTMqoxxMMUERpOR+Q4b1KgncDZkhrO2ql1tAwEIB4h4BBgWCAAgFiEEDM2H44Zo Pt9Ms0eHtVrAHPRh1FwFAmBx6lICGwwACgkQtVrAHPRh1Fw1JwD/Qo7kvtib8jy7puyWrSv0MeTS g8qIxgoRWJE/KKdkCLEA/jb9b9/g8nnX+UcwHf/4VfKsjExlnND3FrBviXUW6NcB X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:240885 Archived-At: Eli Zaretskii writes: > >> From: Philip Kaludercic >> Cc: ane@iki.fi, 57400@debbugs.gnu.org >> Date: Fri, 26 Aug 2022 13:29:22 +0000 >> >> >> Only if the MUA can recognise the patch and pipe it into a git am >> >> process. >> > >> > What do you mean by "MUA can recognize" here? which Emacs MUA >> > recognizes Git-formatted patches and applies them? >> >> The MUA recognizes the patch as a an attachment. E.g. in Gnus the patch >> is highlighted and "|" is bound to a command that pipes the contents of >> the attachment through a command. >> >> > What I do is invoke "M-|" and send the region to "git am". That >> > requires myself to recognize the patches, not the MUA I use. >> >> I hadn't considered that, but again, if we are thinking about preparing >> messages that are sent out to other developers using other MUAs, then I >> don't know if this kind of functionality is available. > > I fail to see how other MUAs used by other developers are relevant > here. We are talking about sending patches, not receiving them. > Sending them as attachments is a known, and frequently required or > preferred, technique. How the patches are handled on the receiving > end is a separate problem, but it already has its solution, because > people send patches as attachments all over the place. But there are plenty of projects that will only accept patches formatted and sent by "git send-email". If you send them an attachment with a patch, they might complain and ask you to send it back again using "git send-email". Once again, I don't think we disagree on anything substantial here. You have already said that it is fine to implement support for both, and everything beyond that should not matter for the proposal.