From: "Clément Lassieur" <clement@lassieur.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 66618@debbugs.gnu.org, Simon Tournier <zimon.toutoune@gmail.com>
Subject: [bug#66618] [PATCH] etc: gitconfig: Remove the default email address to avoid mistakes.
Date: Sun, 22 Oct 2023 22:55:12 +0200 [thread overview]
Message-ID: <87mswav0lr.fsf@lassieur.org> (raw)
In-Reply-To: <87y1fxguxk.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 20 Oct 2023 11:44:39 -0400")
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]).
[0]: https://git-scm.com/docs/git-config#_conditional_includes
Clément
next prev parent reply other threads:[~2023-10-22 20:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 22:23 [bug#66618] [PATCH] etc: gitconfig: Remove the default email address to avoid mistakes Clément Lassieur
2023-10-19 1:34 ` Maxim Cournoyer
2023-10-19 9:46 ` Clément Lassieur
2023-10-19 1:36 ` Maxim Cournoyer
2023-10-19 9:37 ` Clément Lassieur
2023-10-20 1:54 ` Maxim Cournoyer
2023-10-20 8:42 ` Clément Lassieur
2023-10-20 14:06 ` Simon Tournier
2023-10-20 15:44 ` Maxim Cournoyer
2023-10-22 20:55 ` Clément Lassieur [this message]
2023-10-23 0:30 ` Maxim Cournoyer
2023-10-23 9:57 ` Simon Tournier
2023-10-23 14:17 ` Maxim Cournoyer
2023-10-25 20:11 ` Clément Lassieur
2023-10-26 8:31 ` Simon Tournier
2023-10-26 10:38 ` bug#66618: " Clément Lassieur
2023-10-23 9:49 ` [bug#66618] " Simon Tournier
2023-10-23 14:28 ` Maxim Cournoyer
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=87mswav0lr.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=66618@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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/guix.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.