From: Philip Kaludercic <philipk@posteo.net>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: emacs-devel@gnu.org
Subject: Re: master 59df0a7bd9: Add a VC command to prepare patches
Date: Sun, 09 Oct 2022 12:30:40 +0000 [thread overview]
Message-ID: <87r0zh2n7z.fsf@posteo.net> (raw)
In-Reply-To: <87ilkub3w9.fsf@melete.silentflame.com> (Sean Whitton's message of "Sat, 08 Oct 2022 10:51:02 -0700")
Sean Whitton <spwhitton@spwhitton.name> writes:
> Hello,
>
> On Sat 08 Oct 2022 at 05:29PM GMT, Philip Kaludercic wrote:
>
>> Yes, but I would wait a bit to avoid the same issues as we had when
>> `diff-add-log-use-relative-names' was set. Anyone who had pulled the
>> new commits with the change but hadn't rebuilt Emacs to know that these
>> are safe values was prompted the "are you sure these variables are safe"
>> queries. If we wait for a week or two then I would guess that most
>> people following development will have pulled and rebuilt at least once
>> by then.
>
> Cool. Perhaps the docstring for vc-prepare-patches-separately should
> also mention that it can be set locally, then?
I don't think it is necessary, that information is automatically
inserted into the help buffer:
vc-prepare-patches-separately is a variable defined in ‘vc.el’.
Its value is t
Non-nil means that ‘vc-prepare-patch’ creates a single message.
A single message is created by attaching all patches to the body
of a single message. If nil, each patch will be sent out in a
separate message, which will be prepared sequentially.
--> This variable is safe as a file local variable if its value
satisfies the predicate ‘booleanp’.
This variable was introduced, or its default value was changed, in
version 29.1 of Emacs.
You can customize this variable.
[back]
> (Btw, just filed a feature request, but forgot to X-debbugs-cc you.)
bug#58383 I assume?
> Thanks for this cool new feature.
I am glad it is of use.
next prev parent reply other threads:[~2022-10-09 12:30 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0zh2n7z.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=spwhitton@spwhitton.name \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.