Re: master 59df0a7bd9: Add a VC command to prepare patches

[Philip Kaludercic <philipk@posteo.net>]

Sean Whitton <spwhitton@spwhitton.name> writes:

> Hello,
>
> On Sat 08 Oct 2022 at 05:52AM -04, Philip Kaludercic wrote:
>
>> +@vindex vc-prepare-patches-separately
>> +Depending on the value of the user option
>> +@code{vc-prepare-patches-separately}, @code{vc-prepare-patch} will
>> +generate one or more messages.  The default value @code{t} means
>> +prepare and display a message for each revision, one after another.  A
>> +value of @code{nil} means to generate a single message with all
>> +patches attached in the body.
>> +
>> +@vindex vc-default-patch-addressee
>> +If you expect to contribute patches on a regular basis, you can set
>> +the user option @code{vc-default-patch-addressee} to the address(es)
>> +you wish to use.  This will be used as the default value when invoking
>> +@code{vc-prepare-patch}.  Project maintainers may consider setting
>> +this as a directory local variable (@pxref{Directory Variables}).
>> +
>
> Please excuse me if I missed discussion in a bug, but wouldn't it make
> sense to set *both* of these in .dir-locals.el for emacs.git?

Also, a nice feature to add in the future would be if
`vc-default-patch-addressee' could be computed by inferring maintainers
for the files changes (sort of what the Linux kernel also does with the
get_maintainer.pl script).  I don't know of any generic mechanism, but
maybe one could come up with some kind of a standard for the GNU project
and try to promote it for others as well?