From: Robert Pluim <rpluim@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: master 59df0a7bd9: Add a VC command to prepare patches
Date: Mon, 10 Oct 2022 16:18:38 +0200 [thread overview]
Message-ID: <874jwb69tt.fsf@gmail.com> (raw)
In-Reply-To: <87czazapom.fsf@posteo.net> (Philip Kaludercic's message of "Mon, 10 Oct 2022 11:22:33 +0000")
>>>>> On Mon, 10 Oct 2022 11:22:33 +0000, Philip Kaludercic <philipk@posteo.net> said:
>> One surprising thing that isnʼt called out explicitly is that if you
>> do `vc-prepare-patch' for multiple revisions, it prepares the first
>> patch, waits for you to do something with it (like send it), and then
>> moves on to the next. I guess I was expecting it to prepare *all* of
>> them (that way I could just save them all, and look in my drafts
>> folder afterwards, and send them all at once). Maybe 'git
>> format-patch' has spoiled me.
Philip> It would be possible to add either another option or a third value to
Philip> have all messages automatically send out.
I was thinking more along the lines of an option to prepare all the
mail messages and *not* send them out.
Robert
--
prev parent reply other threads:[~2022-10-10 14:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166522273249.875.4607071661972312638@vcs2.savannah.gnu.org>
[not found] ` <20221008095212.D8BB0C21CF8@vcs2.savannah.gnu.org>
2022-10-08 12:03 ` master 59df0a7bd9: Add a VC command to prepare patches Michael Albinus
2022-10-08 12:40 ` Philip Kaludercic
2022-10-08 12:43 ` Michael Albinus
2022-10-08 17:19 ` Sean Whitton
2022-10-08 17:29 ` Philip Kaludercic
2022-10-08 17:51 ` Sean Whitton
2022-10-09 12:30 ` Philip Kaludercic
2022-10-12 22:53 ` Sean Whitton
2022-11-15 19:18 ` Philip Kaludercic
2022-11-16 0:06 ` Sean Whitton
2022-11-16 8:18 ` Philip Kaludercic
2022-10-08 17:32 ` Philip Kaludercic
2022-10-10 10:52 ` Robert Pluim
2022-10-10 11:22 ` Philip Kaludercic
2022-10-10 14:18 ` Robert Pluim [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jwb69tt.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).