[bug#66618] [PATCH] etc: gitconfig: Remove the default email address to avoid mistakes.

[Maxim Cournoyer <maxim.cournoyer@gmail.com>]

Hi,

Clément Lassieur <clement@lassieur.org> writes:

> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hi Simon,
>>
>> Simon Tournier <zimon.toutoune@gmail.com> writes:
>>
>>> Hi Maxim,
>>>
>>> On Thu, 19 Oct 2023 at 21:54, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>>>
>>>> One could argue it's also a misleading documentation.  It should say if
>>>> a 'to' address is not specified *or* configured.  
>>>
>>> Well, personally I prefer: « Explicit is better than implicit. » and
>>> « Errors should never pass silently.  Unless explicitly silenced. ».
>>>
>>> Here, the default
>>>
>>>      [sendemail]
>>>             to = guix-patches@gnu.org
>>>
>>> makes something implicit – which is not necessary bad – but it hides
>>> potential errors – which is not good.
>>
>> But that's true for any automation of git.  If we follow that logic we
>> can remove the other git configurations because they may be surprising,
>> and the send-email hook that notifies people, because that can again be
>> surprising.
>
> Some automation is fine (although maybe not necessary) because it's
> about things we want to enforce (like signed commits).
>
>> Obviously, I'd rather not go that slope.  The small cost in surprise is
>> offset by removing manual work for myself and I'd expect/hope other
>> committers.  Does that make sense?
>
> I don't think there is a need for `--to` automation in Guix repo because
> it's something the user can automate in their own ~/.gitconfig (with
> `includeIf`[0]).

I often have single patches, or with series I need to send the cover
letter first; just writing 'git send-email -1' is shorter
than 'git send-email --to=guix-patches@gnu.org -1' :-).

I also often use patman (info "(u-boot) Patman patch manager") and
there's no way to specify a --to from the command line (you use
Series-to: NNNNN@debbugs.gnu.org as a git trailer after having received
it for a cover letter), which would make things slightly more
annoying...

> [0]: https://git-scm.com/docs/git-config#_conditional_includes

... by having to configure this in a way that matches all my Guix
worktrees spread around :-).

I guess what I'm saying is that it provides value for me, and I'd expect
for others, although I can see how it could generate surprise when you
initially get your 'get send-email' foo wrong.

Perhaps we should more prominently mention that 'mumi send-email' should
be used for first timers, as it's less likely to get things wrong using
it?

-- 
Thanks,
Maxim