From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Supporting git-send-email/hg email in VC Date: Wed, 24 Aug 2022 20:44:53 +0300 Organization: LINKOV.NET Message-ID: <864jy1o7sa.fsf@mail.linkov.net> References: <848rndq2i7.fsf@iki.fi> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="833"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) Cc: emacs-devel@gnu.org, Philip Kaluderdic To: Antoine Kalmbach Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 24 20:02:40 2022 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 1oQui7-00005z-NL for ged-emacs-devel@m.gmane-mx.org; Wed, 24 Aug 2022 20:02:39 +0200 Original-Received: from localhost ([::1]:54616 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oQui6-0006hT-M1 for ged-emacs-devel@m.gmane-mx.org; Wed, 24 Aug 2022 14:02:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42166) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oQuX8-0005EB-LC for emacs-devel@gnu.org; Wed, 24 Aug 2022 13:51:18 -0400 Original-Received: from relay2-d.mail.gandi.net ([2001:4b98:dc4:8::222]:42347) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oQuX6-0006kV-FD for emacs-devel@gnu.org; Wed, 24 Aug 2022 13:51:18 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id 57AB140003; Wed, 24 Aug 2022 17:51:09 +0000 (UTC) In-Reply-To: <848rndq2i7.fsf@iki.fi> (Antoine Kalmbach's message of "Wed, 24 Aug 2022 14:56:00 +0300") Received-SPF: pass client-ip=2001:4b98:dc4:8::222; envelope-from=juri@linkov.net; helo=relay2-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:294044 Archived-At: > If people think this would be a useful feature, I can open a bug report > to track this and start working on it. The proposed reference > implementation for Git would be to (1) ask the user for a ref (2) call > git format-patch with that (3) compose a new message in Emacs, and set > the body of the message to be the output of git-format-patch (OR attach > the file) and (4) let the MUA take it from there. The existing command `submit-emacs-patch' might be helpful as a starting point where you could replace reading of a patch file name with reading of a set of revisions.