From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#57400: 29.0.50; Support sending patches from VC directly Date: Fri, 26 Aug 2022 17:21:19 +0300 Message-ID: <83h71z13xc.fsf@gnu.org> 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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36970"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 57400@debbugs.gnu.org, ane@iki.fi To: Philip Kaludercic Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Aug 26 16:56:15 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 1oRako-0009OA-Dn for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 26 Aug 2022 16:56:14 +0200 Original-Received: from localhost ([::1]:34792 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oRakn-0000EY-DO for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 26 Aug 2022 10:56:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40864) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRaDj-0004H5-Iu for bug-gnu-emacs@gnu.org; Fri, 26 Aug 2022 10:22:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36240) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oRaDi-0005jR-9f for bug-gnu-emacs@gnu.org; Fri, 26 Aug 2022 10:22:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oRaDh-000541-Pm for bug-gnu-emacs@gnu.org; Fri, 26 Aug 2022 10:22:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 26 Aug 2022 14:22:01 +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.166152367619388 (code B ref 57400); Fri, 26 Aug 2022 14:22:01 +0000 Original-Received: (at 57400) by debbugs.gnu.org; 26 Aug 2022 14:21:16 +0000 Original-Received: from localhost ([127.0.0.1]:54219 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oRaCx-00052e-KY for submit@debbugs.gnu.org; Fri, 26 Aug 2022 10:21:15 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:58244) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oRaCv-00052P-6K for 57400@debbugs.gnu.org; Fri, 26 Aug 2022 10:21:13 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36196) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRaCp-0005W5-GZ; Fri, 26 Aug 2022 10:21:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=8+GkyZOSosE94pQSq0RvUlS8q03RX3uTXXNTPmRQJpE=; b=NtThQO80RVHC FyDO56Qvw/d6jQ+gKWSRkFBhRBOz3zqP521kmhXEErkkRX+QRu9OilnOFxqzL20xWkRimVSR3sndO ZJqegBP0VPZsR7SS+1VsNn5cKEVDxzL5Q4bQuRKRkGUmTXzolNJu6Uo0gANsFagPt62zdLsiUJvwJ f71pXd1Nmy/SHfiMSpnkVCFJjKi7xQTtbz7hyzSJGVA56gtpC1oAHB3PLB+BxxRhaS6bz7t1jrAMZ O6/P/Jg+SQNYc2INmWdvUrEAUIvjeTCSpvocJm/VV+tX0LMXuPS7UQKSQul5A5PMhX+9cmX9Xgc2s CQll4o1x8W5Dakx0/qInKw==; Original-Received: from [87.69.77.57] (port=4713 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRaCo-0002RM-St; Fri, 26 Aug 2022 10:21:07 -0400 In-Reply-To: <87y1vbjfpp.fsf@posteo.net> (message from Philip Kaludercic on Fri, 26 Aug 2022 13:29:22 +0000) 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:240843 Archived-At: > 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 if we are trying to re-create the behaviour of "git > >> send-email" (as I think is necessary if we want the feature to be of use > >> outside of Emacs circles, such as sending a patch to the Linux Kernel > >> Mailing List), then we need to consider people using clients like Mutt > >> or Aerc (https://aerc-mail.org/) that just pipe the entire message > >> through "git am". > > > > Do you intend to provide a VC front-end to applying the patch-set, as > > part of this job? Because if not, what happens on the receiving end > > is out of the scope of the feature we are discussing. > > No, this is just about sending patches, but if the patches sent out are > of no use to the developers receiving them, then the feature is not as > useful as it could be. They cannot be "of no use", because these practices are already in use, regardless of whether Emacs does or doesn't support them.