From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Antoine Kalmbach Newsgroups: gmane.emacs.bugs Subject: bug#57400: 29.0.50; Support sending patches from VC directly Date: Fri, 26 Aug 2022 15:08:01 +0300 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40076"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 57400@debbugs.gnu.org To: Eli Zaretskii , Philip Kaludercic Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Aug 26 14:30:10 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 1oRYTS-000AJc-EO for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 26 Aug 2022 14:30:10 +0200 Original-Received: from localhost ([::1]:35270 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oRYTR-000422-At for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 26 Aug 2022 08:30:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52792) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRY90-000164-0z for bug-gnu-emacs@gnu.org; Fri, 26 Aug 2022 08:09:08 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34570) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oRY8z-00075z-NJ for bug-gnu-emacs@gnu.org; Fri, 26 Aug 2022 08:09:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oRY8z-0000m5-Hv for bug-gnu-emacs@gnu.org; Fri, 26 Aug 2022 08:09:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Antoine Kalmbach Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 26 Aug 2022 12:09: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.16615156862914 (code B ref 57400); Fri, 26 Aug 2022 12:09:01 +0000 Original-Received: (at 57400) by debbugs.gnu.org; 26 Aug 2022 12:08:06 +0000 Original-Received: from localhost ([127.0.0.1]:52552 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oRY86-0000kw-F5 for submit@debbugs.gnu.org; Fri, 26 Aug 2022 08:08:06 -0400 Original-Received: from lahtoruutu.iki.fi ([185.185.170.37]:35098) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oRY84-0000km-MV for 57400@debbugs.gnu.org; Fri, 26 Aug 2022 08:08:05 -0400 Original-Received: from qfinm256.local (unknown [66.159.213.92]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: ane) by lahtoruutu.iki.fi (Postfix) with ESMTPSA id 0965D1B001A3; Fri, 26 Aug 2022 15:08:01 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=lahtoruutu; t=1661515682; 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=h9T/CxzmtzzZ5hdxv6vOKSpom383IT4/xPma8fzAwcA=; b=LEgXK4FTMxq50Wrmp/qVZtQemT2d6PRI4C9pAxZSt2WumyAurNV6UTD+mD5PzOjjkHjh3y 5tFyoR/BOd/MA6UwHnLlBlj6Yezw5tJ0g4E1uOS9XG3ikXjK8bc0yceamTbUY9aF88gNaF am7RIW0VHj+nbeoKhIX727ieEbVAhFRjthE8gSBQ9mgGWBJutG5N2phvDk6Vaj+iPAWrep nV5fAlG7AxuWEgSwhvS7A8u0dKs4Z/e6WKNDWi0IflKtHMcURWFFEB+Rc5qyZkU41sXfl7 aTQGru/p9ClXJWBs8M7b4iGaY78PJFELA9bVKUtIwJmZUCSi6Q/t2m3LFVfQhg== In-Reply-To: <83mtbr1b6l.fsf@gnu.org> ARC-Seal: i=1; s=lahtoruutu; d=iki.fi; t=1661515682; a=rsa-sha256; cv=none; b=hPQJ9rSANsWiWoxhsFSYepuVMw6e7Q+NwwwSGekS9EZdarmJCoXesg5aNk9H3OWE10y/Zi JDdLJ7GE30C1H4RXQSK1vuAu2EqGnVRwg/JQRguTvOLfV6jViG9luLb6AY8+YI/KiKqoBF 8b68bvmAtTcxOKL5x7yH+ODgEO0IJTAMlIqVBvu+H6VvL9CavAzwmfArjpzIJxjyim3BBp SyBlcFwkCiHNS26+IzUJkcpcWT+7EAwRw7A3Q1ZUTMcGibwQikxZN1fYHLkb7MD0o3MSPE dhsuFio/Wk1vQQRbEAYksy5pdGjoW6x6aezjRaHkgtyVqCYeULEO2iejZi2UMQ== ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=ane smtp.mailfrom=ane@iki.fi ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=lahtoruutu; t=1661515682; 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=h9T/CxzmtzzZ5hdxv6vOKSpom383IT4/xPma8fzAwcA=; b=wcd7/vHNKbEiTNo83IVf7XIQD7gG+918G1ACSYTJ8y64ubnyJ+cfdYyS8vNFO/+KvKeLKD l86r5LTebZueimX6AjRMx4wL+HExoDqIRu7r5VU2Tn7cM5SoQDLTJ8G/9LoubyWr9B8cEO F3y6hFoHAlz/p47GRlf1VbTpFLEULLfgu3RULXMiw1y9iiUZU6EtjbXdlocXeqGpPJv4RP ngtlk50qIHmzv0nmr9qijBj0DZuT/CGljtLzQjjv/PR65wneNUOnmIbsq6OO9uO7p0SHSX 0YZ3FSfcR7EHOffaSCAPRVHnSHi/DauuhM+AJDjlpvl2LH5ls8pUSiC6PWmDIA== 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:240825 Archived-At: Eli Zaretskii writes: >> > Also, I'm not sure why we'd need to send each patch file separately. >> > Why not add them one by one as attachments to the same email message? >> >> This wouldn't work if we are sending patches to a mailing list that >> assumes patches are sent out by git send-email, and that the messages >> can be filtered through git am. > > "git am" handles attachments without any problems, I do it all the > time. > But you have to save the attached .patch files and then run git am on those. Typically, without attachments, you'd run `git am` on the message (mbox) directly. Each mail is a patch in that sense, and a separate cover letter is sent first when there's some introductory words that need to be said. > But I don't object to having optional behaviors here. My point is > that we should allow sending all the patches together, as that is the > preferred/usual practice in Emacs development. Yes, but users would have to apply the customization to get the Emacs way of working, I think. -- Antoine Kalmbach