From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 66618@debbugs.gnu.org
Subject: [bug#66618] [PATCH] etc: gitconfig: Remove the default email address to avoid mistakes.
Date: Thu, 19 Oct 2023 21:54:38 -0400 [thread overview]
Message-ID: <87zg0em529.fsf@gmail.com> (raw)
In-Reply-To: <eb66f90d-e7f0-4836-8bba-01a9affdd021@app.fastmail.com> ("Clément Lassieur"'s message of "Thu, 19 Oct 2023 09:37:20 +0000")
Hi,
Clément Lassieur <clement@lassieur.org> writes:
>> > This just happened to me twice in a row, so I imagine it could happen to some
>> > other people as well.
>>
>> That's part of learning 'git send-email', I'd think :-). On a positive
>> note, now you get to learn how to use Debbugs for the same price ;-).
>
> People don't expect their git/config to be modified in such
> substantial ways. It's already difficult for new comers to use git
> send-email well, please don't make it harder. (And I'm not even
> talking about the crash.)
>
> There this git send-email feature:
>
>> The header of the email is configurable via command-line
>> options. If not specified on the command line, the user will be
>> prompted with a ReadLine enabled interface to provide the necessary
>> information.
>
> that has been removed with your patch. I call this a bug.
One could argue it's also a misleading documentation. It should say if
a 'to' address is not specified *or* configured. What would you have
typed interactively if prompted; guix-patches@gnu.org? :-) I think you
might grow to like this default after this initial mishap.
> I prefer the "wontfix" tag if you really don't want to amend your patch. :-)
OK! I'll leave this opened for a bit longer to allow for others to tip
in, after which I'll do so.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-10-20 1: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 [this message]
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
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=87zg0em529.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=66618@debbugs.gnu.org \
--cc=clement@lassieur.org \
/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.