From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#57400: 29.0.50; Support sending patches from VC directly Date: Fri, 7 Oct 2022 01:10:32 +0300 Message-ID: <8fa87ad2-6d5c-2f9d-ed37-0b956fbadd2c@yandex.ru> References: <84v8qgn1z9.fsf@iki.fi> <87h71zo3p8.fsf@posteo.net> <87sfljmgwz.fsf@posteo.net> <87y1twvima.fsf@posteo.net> <84sfk2p846.fsf@iki.fi> <87h70i9ntt.fsf@posteo.net> <87edvl6vbj.fsf@gmail.com> <8735c1nn3y.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24797"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Cc: 57400@debbugs.gnu.org, Antoine Kalmbach To: Philip Kaludercic , Robert Pluim Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Oct 07 00:11:26 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 1ogZ5S-0006GR-F1 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 07 Oct 2022 00:11:26 +0200 Original-Received: from localhost ([::1]:52334 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ogZ5R-0001ox-DI for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 06 Oct 2022 18:11:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36264) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogZ54-0001ni-1F for bug-gnu-emacs@gnu.org; Thu, 06 Oct 2022 18:11:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34672) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ogZ53-0003fO-PI for bug-gnu-emacs@gnu.org; Thu, 06 Oct 2022 18:11:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ogZ53-00079Y-J1 for bug-gnu-emacs@gnu.org; Thu, 06 Oct 2022 18:11:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 06 Oct 2022 22:11: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.166509424327467 (code B ref 57400); Thu, 06 Oct 2022 22:11:01 +0000 Original-Received: (at 57400) by debbugs.gnu.org; 6 Oct 2022 22:10:43 +0000 Original-Received: from localhost ([127.0.0.1]:33749 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ogZ4k-00078x-TX for submit@debbugs.gnu.org; Thu, 06 Oct 2022 18:10:43 -0400 Original-Received: from mail-wr1-f46.google.com ([209.85.221.46]:37602) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ogZ4i-00078c-Cf for 57400@debbugs.gnu.org; Thu, 06 Oct 2022 18:10:41 -0400 Original-Received: by mail-wr1-f46.google.com with SMTP id bv10so1100370wrb.4 for <57400@debbugs.gnu.org>; Thu, 06 Oct 2022 15:10:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date; bh=zD+UUs6vQ9TLA5KchejJfdi5Y7fv4f+qfur2EwWpNI8=; b=lARW7wW6KYGv0ul5RqqieNJHw8Z5fSYkJk/QxFroDpniR2ixEWEQd995cz8D4sbHDz EUOPkVQgZtYnLczEntm4I8XM+WUK5zDy3KFbfxMvsk8Msak39QA3W11UoElP3rKNFayP uJYKpQwhR35m8M+JZulE4OO2H96yrlRurvGFdimM2MxA2YKyGJBpIdfO0QZH7RQnNaUC vsV9JACEVJzCpn1H7EHG5GIA3YwwqXmQoexE1wjJX/h62xXPA28Fu4hcWwDS6RSS9ZQm mvfOkM/xQ2wNF1I3ZCH06xSQGi9A3T5RNtsPqG+XC08SKP6A0X3RBOMj5JCC3P5uXQE3 25kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date; bh=zD+UUs6vQ9TLA5KchejJfdi5Y7fv4f+qfur2EwWpNI8=; b=k5xJEAevMhOhYh+l3FJBTf0wPj8l8MXPjojDa59roMVParIH99LoKdzUUM7mpcVQJz Uw6HMNRc0muU6hk9an8gOdn9lgPFSlwiWN8Uf0x3KiQjhpl4FUqkeDSFHy9kYdGUPLzd BeD4n/g6r/0BsldQsovd1uvEKfzkW7kUucSS+oPc4CEoxXIGNXBeUuvShW1MZovmgyrM fV2EG5aZHvfH+ITyPLYo/TH51qftVDlSrEopoEe/p8wfFzm17rYeGxsQn8+/GPDwnh8A X/0LGOVoke3RLIdWxPF0Ig3XI34MvhpVCgYxyOQIp/5Y9HB1TTE9yERSj0VoCQulFZzg BfPQ== X-Gm-Message-State: ACrzQf28kKPhhR5sElmSFD6sl4STZuTQtRlcZJajl/kk2OPO55zJySj8 zcvYBc4bAmqWzIu94dhyekg= X-Google-Smtp-Source: AMsMyM7nYASuxAtihDnfIdgO185CEGKf6uAByj2xvnBzzCRgesmUzTAR29pVtEgmaBPk+XW7ZbpAVg== X-Received: by 2002:a5d:5148:0:b0:22e:53bd:31c5 with SMTP id u8-20020a5d5148000000b0022e53bd31c5mr1214869wrt.241.1665094234280; Thu, 06 Oct 2022 15:10:34 -0700 (PDT) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id iv19-20020a05600c549300b003b47b913901sm17967492wmb.1.2022.10.06.15.10.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 06 Oct 2022 15:10:34 -0700 (PDT) Content-Language: en-US In-Reply-To: <8735c1nn3y.fsf@posteo.net> 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:244713 Archived-At: Hi Philip, On 06.10.2022 15:38, Philip Kaludercic wrote: > I'm glad to hear that. Here is the updated patch: This version resolves the main questions I had as well. Here's one more, though: the way I normally used 'git format-patch' is I pass just one ref, and that's usually the name of the branch to start the history at (the argument from the manual). So I never had to "type revisions in the Git syntax" for this to work, something Eli was worried about. Should this new command support this usage as well? The range of revisions could be fetched by passing the base revision as LIMIT to the 'print-log' action (like vc-log-mergebase does), but how the updated calling convention for vc-prepare-patch will look is not obvious to me.